Skip to main content
Glama

Search the API scoreboard (free)

scoreboard_search
Read-only

Free. Search/browse the scoreboard of paid agent APIs with filters; sorted by score.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "scoreboard_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoText search in name, description and URL.
limitNo
offsetNo
protocolNo
data_typeNo
min_scoreNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuinely useful non-annotation context: there is no payment/credential cost ('Free') and results come back ordered by score, which affects how an agent should present or paginate them. It stops short of covering rate limits or what fields each result carries.

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?

A single tight sentence with the most decision-relevant fact ('Free') front-loaded and no filler. Nothing is wasted, though the brevity is part of why coverage is thin elsewhere.

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

Completeness3/5

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

For a zero-required-parameter read-only discovery call with no output schema, the definition states enough to make a first call, but it leaves the agent guessing at page-shape and at the meaning of the two enum filters. Given the low schema coverage, a sentence on filter behavior or result contents would have closed the gap.

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

Parameters2/5

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

Schema description coverage is only 17% – just the q parameter is documented – and the description does not compensate. It says 'with filters' but never explains protocol (L402 vs x402), data_type selection, or how min_score interacts with the score-based sort, leaving five of six parameters semantically thin.

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 pairs a specific verb ('Search/browse') with a specific resource ('the scoreboard of paid agent APIs') and states the result ordering ('sorted by score'). It is clear what the tool returns a list of, though it never names the sibling it is distinct from (scoreboard_endpoint for a single API).

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing tells the agent to prefer scoreboard_categories for taxonomy browsing, scoreboard_endpoint for a single API's details, or best_endpoint for a top pick. The word 'Free' hints at cost but not at routing between alternatives.

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