Skip to main content
Glama

Agent Data Tools: Full list (every tool as its own definition)

API recommendation: which API to call for a task

recommend
Read-only

Describe a task in plain words and get the best-matching paid API calls for it from a catalog of 600+ tools (web search and page reading, LLM chat, token prices and EVM chain reads, sanctions and company checks, weather, finance and utilities): each pick with the exact call URL, required inputs, price, MCP tool name and whether it is in the free calls. Use when an agent needs to find which API to call before paying for one. Example: need=current gas price on Base. Price $0.002/call via x402 USDC or a card key (/credits), first 25 free; failed calls free. Reads or computes only and changes nothing; each call is charged, so repeats are not free.

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": "recommend"
  }
}

Input Schema

NameRequiredDescriptionDefault
needYesThe task in plain words, up to 300 characters
countNoHow many picks, 1 to 5 (default 3)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the annotations (readOnlyHint, openWorldHint, destructiveHint=false), the description discloses the commercial model in detail: $0.002/call via x402 USDC or a card key at /credits, first 25 free, failed calls free, and that repeats are not free. The last point usefully corroborates idempotentHint=false, and 'reads or computes only and changes nothing' confirms the non-destructive profile.

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?

The core purpose and the 'before paying' trigger are front-loaded, and pricing details follow logically. The long parenthetical catalog enumeration and the clause 'reads or computes only and changes nothing' (which largely restates readOnlyHint) are the least efficient parts.

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?

With no output schema, the description carries the return-shape burden and does so fully: each pick includes the exact call URL, required inputs, price, MCP tool name, and free-call status. Combined with cost, payment paths, and the 1–5 pick limit in the schema, an agent has everything needed to call and interpret this tool.

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 description coverage is 100%, so baseline is 3. The description adds a modest amount — the worked example shows the plain-language style expected for `need`, and 'each pick' implies the role of `count` — but it never explains the count range/default or the 300-character limit, leaving that entirely to the schema.

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 specific verb and resource: 'Describe a task in plain words and get the best-matching paid API calls.' It further distinguishes the tool from siblings by enumerating the catalog scope (600+ tools: web search, LLM chat, chain reads, sanctions checks) and by returning call URLs and MCP tool names, so an agent can see this is a recommendation/routing tool rather than an execution or search tool.

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: 'Use when an agent needs to find which API to call before paying for one,' and reinforces it with a concrete example (need=current gas price on Base). It does not, however, name alternatives or state when not to use it — e.g., whether to go directly to base_call/eth_call/token when the capability is already known.

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.