Skip to main content
Glama

Score details for one API (free)

scoreboard_endpoint
Read-only

Free. Score components, probe stats and recent probe history for one scoreboard entry (id from best_endpoint/scoreboard_search).

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": {
      "id": "<id>"
    },
    "name": "scoreboard_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/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 safety is covered structurally. The description adds useful context not in the annotations: the call is free and returns probe history as well as current stats. It does not say how far back the history goes, whether results are paginated, or how large a response is.

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?

One sentence with the cost signal front-loaded and the payload enumerated in order of relevance. Nothing is padded and there is no restatement of the tool name.

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 simple single-parameter read tool with no output schema, the description adequately covers what comes back by naming the three data groups. The missing pieces are history window and response size, which matter but are secondary for this complexity level.

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 0%, so the single parameter is undocumented in the schema and the description must compensate. It does add meaning by specifying that id is a scoreboard entry identifier obtained from best_endpoint or scoreboard_search. It does not state format or validation, so the compensation is only partial.

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 names the concrete payload (score components, probe stats, recent probe history) for a single named resource, a scoreboard entry. It also says where the entry comes from, which lets an agent distinguish this from best_endpoint and scoreboard_search. It stops short of an explicit verb, so it is clear but not maximally sharp.

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?

"id from best_endpoint/scoreboard_search" gives a clear precondition and implicitly points at the upstream siblings to call first. There is no explicit "when not to use" or statement about alternatives for the details themselves, so it falls just short of full routing guidance.

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