Skip to main content
Glama

Find the benchmark that answers a question

search_benchmarks
Read-onlyIdempotent

Ranks the benchmark catalogue against a question in the user's own words and returns the best few matches.

Use this when somebody asks which provider, chain or service is fastest, cheapest, most reliable or best for something. Pass their phrasing through: provider names, chain names and goals all match.

• "which Solana RPC is fastest" -> search_benchmarks({ query: "solana rpc" }) • "Alchemy or Quicknode on Base?" -> search_benchmarks({ query: "alchemy quicknode base" }) • "cheapest way to bridge to Arbitrum" -> search_benchmarks({ query: "bridge arbitrum" })

Returns compact rows. Open the one you want with get_benchmark for the full ranking and a citation line. An empty result means nothing is measured for that question; say so rather than guessing.

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": {
      "query": "<query>"
    },
    "name": "search_benchmarks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matches, 1 to 25. Default 8.
queryYesThe user's question or keywords, verbatim. Provider and chain names work well.
categoryNoOptional category filter: RPCs, Trading, Bridges, Blockchains, Aggregators, RWA, NFT APIs.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already cover read-only, idempotent and open-world behavior, so the description instead adds what the annotations cannot: that results are 'compact rows', that an empty result signals an unmeasured question, and that the agent should say so rather than guess. It does not mention ranking/scoring mechanics or result ordering beyond 'best few', which is the only remaining gap.

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?

Front-loaded with the core action, followed by a when-to-use sentence, three short examples and a closing note on the return/handoff path. Every block earns its place and nothing is redundant with the schema.

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 steps in to describe the return shape ('compact rows') and the follow-up tool for full detail, and covers the empty-result edge case. That is everything an agent needs to call this tool and interpret the response 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 real meaning beyond the schema by showing that provider names, chain names and goal terms can be combined in one query string ('alchemy quicknode base', 'bridge arbitrum'). It says nothing about limit or category, which the schema already documents.

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?

States a specific verb and resource ('ranks the benchmark catalogue against a question') plus the output shape ('best few matches'). It also implicitly separates itself from get_benchmark and list_benchmarks by describing ranking against free-text rather than listing.

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 when-to-use ('which provider, chain or service is fastest, cheapest, most reliable'), three concrete query examples, and an explicit handoff to get_benchmark for full rankings. It also tells the agent how to phrase the call ('pass their phrasing through').

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.