Skip to main content
Glama

track_record

Return the closed-forecast record of a speaker or institution: counts of met, partial and not met, and a hit rate per register area. Uses public and MCP-only entries, never internal ones. Signetex grades evidence and issues no true/false verdicts.

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

Input Schema

NameRequiredDescriptionDefault
speakerNoName of the person or official speaker to match (case-insensitive, partial match allowed).
institutionNoName of the institution or organisation to match (case-insensitive, partial match allowed). Alias: organisation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations supplied, the description carries the full disclosure burden and does more than most: it states the data provenance (public and MCP-only entries, never internal), and clarifies the grading policy (Signetex grades evidence and issues no true/false verdicts), which prevents an agent from misreading hit rates as verdicts. Gaps remain around behavior with ambiguous matches, zero matches, or calls with no parameters at all.

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?

Three tight sentences, front-loaded with the resource and return contents, followed by scope and grading policy. No filler, though the final grading-policy sentence sits slightly apart from the operational core.

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 two-parameter, read-only aggregation tool with no output schema, the description covers what the tool returns and where the data comes from, which is most of what an agent needs. It does not say what happens when both optional parameters are omitted or when a name matches multiple entities, which is a real gap for a zero-required-parameter tool.

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 coverage is 100%, so both parameters are already documented (case-insensitive partial matching, and the 'organisation' alias), and the description adds no further detail about them. The phrase 'per register area' hints at output grouping rather than parameter meaning. Baseline 3 applies when the schema does the explanatory work.

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 opens with a specific verb and resource ('Return the closed-forecast record of a speaker or institution') and even names the return contents (met/partial/not met counts plus a hit rate per register area), so an agent knows exactly what it produces. It does not explicitly contrast itself with siblings like compare_forecasts or evidence_grades, so it falls short of the top mark.

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

Usage Guidelines3/5

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

Usage is only implied: an agent can infer this is the tool for evaluating a speaker's or institution's forecast history, and the 'public and MCP-only entries, never internal ones' line scopes the data source. There is no explicit statement of when to prefer it over compare_forecasts or evidence_grades, and no prerequisites or exclusions.

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