IndieStack

find_compatible

Read-only

Find compatible tools for your selected technology to build reliable tech stacks. Get agent-verified integrations, conflict warnings, and proven multi-tool combinations from real integration reports.

Instructions

Find tools that are known to work well with a specific tool.

Call this after selecting a tool to discover what pairs well with it. Returns compatible tools grouped by category, with integration report counts, verified stacks (3+ tools proven together), and conflict warnings.

Use this for stack assembly: pick your first tool, then find_compatible() to build around it. Much more reliable than guessing — these are agent-verified integrations.

Args: slug: The tool's URL slug (e.g. "supabase"). Get slugs from find_tools() results. category: Optional category to filter companions (e.g. "authentication"). min_success_count: Minimum number of integration reports (default 1).

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "find_compatible"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes
`category`	No
`min_success_count`	No

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.16.0Apr 6, 2026

TDQS

A4.8/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only declare readOnlyHint=true. Description adds valuable return structure context ('grouped by category, with integration report counts, verified stacks... and conflict warnings') and data provenance ('agent-verified integrations'). Does not cover error cases or pagination, but output schema exists to cover return details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Well-structured with front-loaded purpose statement, followed by invocation timing, return value summary, workflow pattern, and parameter documentation. No redundant sentences; every line advances understanding of tool usage or semantics.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Comprehensive coverage given 3 parameters with no schema descriptions and existing output schema. Description addresses all parameters, provides workflow context, and explains return value categories. Sufficient for agent to invoke correctly without consulting external documentation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema has 0% description coverage. Description fully compensates via Args section: slug includes example ('supabase') and source ('find_tools() results'), category includes purpose ('filter companions') and example ('authentication'), min_success_count explains semantics ('integration reports') and default.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Specific verb 'Find' with clear resource 'tools' and scope 'known to work well with a specific tool'. Effectively distinguishes from siblings like find_tools (general search) and check_compatibility (pairwise checking) by focusing on companion discovery post-selection.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicit workflow guidance: 'Call this after selecting a tool', 'Use this for stack assembly: pick your first tool, then find_compatible() to build around it'. Also specifies input source dependency: 'Get slugs from find_tools() results'. Contrasts with guessing alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.