Skip to main content
Glama

Tool finder

tool_finder
Read-onlyIdempotent

Search the 37,000+ MCP registry & 2,500+ OpenAPI directory for APIs and MCP servers by plain-English task. $0.003 per call over x402 (USDC on Arc, Base or Solana, or XNT on X1). Call once without payment for the terms, sign them with your own wallet, call again with payment.

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": {
      "q": "<q>"
    },
    "name": "tool_finder"
  }
}

Input Schema

NameRequiredDescriptionDefault
qYessearch query, e.g. weather forecast
kindNoany (default), mcp or api
limitNo1-20 (default 10)
paymentNoa signed x402 payment (the base64 payload you would put in PAYMENT-SIGNATURE). Pass it and the purchase completes inside this tool call.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior1/5

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

The annotations declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, yet the description explicitly states that passing `payment` causes 'the purchase completes inside this tool call' and that each call costs $0.003. That is a real, caller-visible side effect (funds transferred, and each repeat call is separately charged), directly contradicting the read-only/idempotent safety profile an agent would rely on to call it without confirmation. The pricing detail is useful, but it exposes the annotation claim as misleading rather than supplementing it.

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?

Three short sentences, front-loaded with the search capability before the cost and the invocation protocol; nothing is padding. The payment sentence is slightly compressed ('Call once without `payment` for the terms') and could be one clause clearer, but the structure is efficient.

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?

For a 4-parameter tool with full schema coverage and no output schema, the description covers capability, cost, auth method, and call sequencing — the things an agent most needs. It does not describe the shape of the results (what a hit looks like) or what the unpaid 'terms' response contains, which leaves a modest gap.

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 description coverage is 100%, so the baseline is 3, but the description adds real meaning the schema lacks: it states the price, the accepted payment assets (USDC on Arc/Base/Solana, XNT on X1), and the two-step 'discover terms, then resubmit with payment' protocol for the `payment` parameter. It does not clarify `kind` or `limit` beyond the schema, so it is not a full 5.

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 gives a specific verb ('Search') plus the exact corpora being searched ('37,000+ MCP registry & 2,500+ OpenAPI directory for APIs and MCP servers') and the query style ('plain-English task'). The stated scope of the corpus also implicitly separates it from the arc_*-prefixed Arc-specific search tools, so an agent can tell what it does without opening the schema.

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

Usage Guidelines3/5

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

There is solid procedural guidance ('Call once without `payment` for the terms, sign them with your own wallet, call again with `payment`'), which tells the agent how to invoke it. However, there is no guidance on when to prefer this tool over alternatives, nor any exclusion such as when a local/Arc-native search is the better choice — the agent must infer selection from the corpus description alone.

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