Skip to main content
Glama

National Capability Benchmark

Read a decision

get_decision
Read-onlyIdempotent

Read one entry of the decision record by number, for example D1 or D118: the methodological choice, why it was made, what it costs and what evidence would overturn it. Use it to answer "why does the benchmark do X?".

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

Input Schema

NameRequiredDescriptionDefault
idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety and determinism profile is covered structurally. The description's real addition is disclosing the shape of the returned entry, which is valuable given no output schema, but it says nothing about behavior when the id does not exist or falls outside the valid set.

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?

Two sentences, front-loaded with the identity of the resource before the return-content detail and the use case. Nothing is redundant with the name or title, and every clause carries information.

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 single-parameter read tool with no output schema, the description is close to self-sufficient: it names the lookup key and enumerates the fields inside a decision entry. Missing only a note on what happens with an unknown or malformed id.

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 0%, so the description must carry the burden, and it does: "by number, for example D1 or D118" directly explains the required `id` string and its ^[dD]\d{1,4}$ pattern. The only shortfall is that case sensitivity and the bounds of the numeric range are left for the agent to infer from the examples.

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 and resource ("Read one entry of the decision record") plus the exact scope of a single entry indexed by number. It then enumerates the content of the entry (the methodological choice, rationale, cost, and falsifying evidence), so an agent can tell it apart from get_country, get_limit, or search_indicators without opening any schema.

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 supplies a concrete use case ("Use it to answer 'why does the benchmark do X?'"), which is more than a restatement of purpose. It does not state exclusions or name an alternative for listing many decisions at once, so the alternative-seeking guidance is implied rather than explicit.

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