compare_tools

Agents typically reach for compare_tools after the user has narrowed to two candidates and wants an opinionated answer rather than a pros/cons dump.

Input

tool_a················································································stringrequired

First tool.

tool_b················································································stringrequired

Second tool.

use_case················································································stringoptional

Context that influences the recommendation weighting.

project_config················································································objectoptional

Current project constraints (language, framework).

Example

{
  "tool_a": "Prisma",
  "tool_b": "Drizzle",
  "use_case": "type-safe ORM for a TypeScript serverless app"
}

{
  "tool_a": { "name": "Prisma", "health_tier": "Thriving", "maturity": "stable" },
  "tool_b": { "name": "Drizzle", "health_tier": "Active",   "maturity": "stable" },
  "dimensions": [
    { "axis": "Type safety",       "winner": "tie"    },
    { "axis": "Serverless cold-start", "winner": "tool_b" },
    { "axis": "Ecosystem size",    "winner": "tool_a" },
    { "axis": "Migration tooling", "winner": "tool_a" }
  ],
  "recommendation": "tool_b",
  "rationale": "For serverless-first TS apps, Drizzle's lighter runtime and direct SQL give better cold-start and equal type safety. Pick Prisma when you need the broader plugin ecosystem."
}

Related

• check_compatibility — after you've picked a tool, check it against the rest of the stack.