Skip to main content
Glama

EasyCanDo

Find chains

find_chains
Read-onlyIdempotent

Find tools that turn one kind of input into another: single tools that do it in one capability, and chains of two tools in a row with the type passed between them. Use it when search_tools finds no single tool for a step. Give a query saying what the chain is for, so the best chains come first.

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": {
      "have": "<have>",
      "want": "<want>"
    },
    "name": "find_chains"
  }
}

Input Schema

NameRequiredDescriptionDefault
haveYesWhat the step starts with. One of: words (words: text, query, message, social-post); photos (photos and images: image, image-mask, 3d); video (video: video); sound (voice and sound: audio-speech, audio, audio-music, audio-sfx); documents (documents: document); links (web links: url, webpage); places (places: geo); data (numbers and data: structured, timeseries, event-stream, embedding); code (code: code); money (money: money); people (people: profile); dates (dates and events: schedule). A type id in parentheses also works, and stands for the id before it.
wantYesWhat the step should produce. One of: words (words: text, query, message, social-post); photos (photos and images: image, image-mask, 3d); video (video: video); sound (voice and sound: audio-speech, audio, audio-music, audio-sfx); documents (documents: document); links (web links: url, webpage); places (places: geo); data (numbers and data: structured, timeseries, event-stream, embedding); code (code: code); money (money: money); people (people: profile); dates (dates and events: schedule); done (something done: action:publish, action:message, action:money, action:world, action:software, action:browser, action:schedule, action:record, physical-item). A type id in parentheses also works, and stands for the id before it. “done” means the tool acts: it posts, sends, pays, books or changes something.
limitNoTools and chains to list of each kind, 1 to 10. Default 5.
queryNoWhat the chain is for, in a few words, like “post clips to tiktok”. Both lists then hold only what the query fits, best first; without it, chains rank by how well the two tools fit the step, then by notability.

Output Schema

NameRequiredDescriptionDefault
haveYes
wantYes
one_stepYesTools that do the whole step in one capability, best first.
ranked_byYes
two_stepsYes
one_step_totalYes
two_steps_totalYes
one_step_matchingYesWith a query, how many of the single tools match it; one_step lists those. 0: none does, and one_step lists the most notable. Null without a query.
two_steps_matchingYesWith a query, how many chains fit it; two_steps lists only those. Null without a query.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety is covered. The description adds behavior beyond that: results come as two lists (single tools and two-tool chains) and ranking follows the query, otherwise fit and notability. Return shape detail is appropriately left to the output schema.

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?

Three short sentences, each with a distinct job: capability, usage trigger, and query guidance. The key scoping statement is front-loaded and nothing is padded.

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

Completeness4/5

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

With a full-coverage schema, an output schema, and complete safety annotations, the description only needs to add purpose and routing, which it does. The minor gap is that it does not clarify how 'limit' splits across the two lists, though the schema's wording covers the count.

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

Parameters3/5

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

Schema coverage is 100%, including exhaustive enum descriptions for have/want and the query/limit semantics, so the schema carries the parameter burden. The description only restates the query's purpose ('Give a query saying what the chain is for, so the best chains come first') and does not add syntax or edge-case meaning beyond it.

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?

The description states a concrete verb and resource ('Find tools that turn one kind of input into another') and narrows the scope precisely: single tools that do it in one capability, plus two-tool chains with the intermediate type. That is distinguishable from a generic search tool without opening either schema.

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

Usage Guidelines4/5

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

It gives an explicit trigger and names the alternative: 'Use it when search_tools finds no single tool for a step,' which tells the agent to prefer search_tools first. It stops short of stating when not to use it or pointing to get_tool for follow-up detail, so it is clear context rather than full routing logic.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources