Skip to main content
Glama

Get Scoreboard

get_scoreboard
Read-onlyIdempotent

Every dated public call The White Report has made, its grade date, and its grade (null while pending). Start here for the track record in human-readable form; use calls_list instead for the sealed machine-format envelopes (wr.calls.v1) behind the same calls. Takes no parameters. Returns the scoreboard exactly as published in the site's calls file — the same record the website shows, with grade null on calls still pending grading. Behaviour: read-only and public — no authentication or API key; every call is logged in aggregate (tool name, result count, coarse client class; no IP addresses).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.9/5.0
Behavior5/5

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

Beyond the readOnly/idempotent/non-destructive annotations, it discloses no authentication or API key is required and that every call is logged in aggregate (tool name, result count, coarse client class, no IP addresses). It also clarifies that pending calls carry a null grade, which is the behavior an agent most needs to interpret results correctly.

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?

It is front-loaded with the resource and the sibling routing rule, then behavior and privacy notes. The pending-grade behavior is stated twice ("null while pending" and again at the end), which is a minor redundancy but not harmful.

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 provided, the description carries the return-value burden and does so: it explains the scoreboard mirrors the site's published calls file and how pending grades appear. Combined with the auth and logging disclosures, an agent has everything needed to call and interpret it.

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

Parameters5/5

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

The tool takes zero parameters and the description states plainly that it takes none, removing any ambiguity for an agent that might otherwise look for filters. There is nothing further a zero-parameter schema could require the description to add.

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 first sentence names the exact resource and fields returned: every dated public call, its grade date, and its grade (null while pending). It also explicitly distinguishes itself from the sibling calls_list by calling out the human-readable track record versus the sealed machine-format envelopes.

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?

The description says "Start here for the track record" and gives an explicit alternative with the condition that selects it: calls_list for wr.calls.v1 envelopes behind the same calls. That is a direct when-to-use/when-to-use-the-other routing rule.

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.