Skip to main content
Glama

claw.mobile AI tools catalogue

Find a tool for a need

find_tool
Read-only

Match a plain-language need (e.g. "cheapest AI app builder with a free plan", "terminal coding agent under $25") to tools in the catalogue. How it ranks: Keyword match over the catalogue, no model involved. 1) Words in the request set filters: "app builder"/"no-code"/"no code" -> type App Builder; "ide"/"editor" -> AI IDE; "terminal"/"cli" -> Terminal Agent; "free" -> only tools with a free plan; "under $N"/"below $N"/"less than $N" -> starting price at most $N; "beginner"/"non-coder"/"non-technical" -> skill level Beginner. 2) Remaining tools are scored by how many other request words appear in the name, bestFor, features and type. 3) Order: if the request says cheap/cheapest/budget/affordable, lowest starting price first; otherwise highest match score, then claw.mobile rating (unrated last), then lowest starting price. Starting price is the first dollar figure the vendor lists, which may be an annual-billing rate or per user. The response repeats the filters it read from the request.

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": {
      "need": "<need>"
    },
    "name": "find_tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesWhat the person wants, in their words
limitNoHow many results (default 5)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior5/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses the full mechanism: keyword matching with no model involved, the exact filter triggers, the scoring signal fields, and the tie-break order. It also flags a real caveat that starting price may be an annual-billing rate or per user, which an agent could not learn from annotations or schema.

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

Conciseness4/5

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

Purpose is front-loaded, then the ranking logic is laid out in numbered steps with quoted trigger phrases, which is easy to scan. It is dense but nearly every clause carries operational information; only the closing note about echoing filters is slightly tangential.

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 no output schema, the description does some of that work by stating the response repeats the parsed filters and implying results carry name, price and rating. It stops short of describing the result object's fields, but the ranking and filter semantics are complete enough to call the tool correctly.

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

Parameters4/5

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

Schema coverage is 100%, so the baseline is 3, but the description adds genuine meaning by explaining how the 'need' string is parsed into filters and how price phrases like 'under $N' are interpreted. The 'limit' parameter is left to the schema, which is acceptable given its full description there.

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

Purpose4/5

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

The description opens with a specific verb and resource: match a plain-language need to tools in the catalogue, with two concrete example queries. It is unambiguous what the tool does, but it never names a sibling (e.g. list_tools or get_tool) to draw the boundary, so it falls short of full sibling differentiation.

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?

The example needs ("cheapest AI app builder with a free plan", "terminal coding agent under $25") make the intended use case concrete and show the expected input style. There are no explicit exclusions or pointers to alternatives, so an agent must infer that structured lookups belong to get_tool or tool_pricing.

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