Skip to main content
Glama

A pundit's NFL record

pundit_record
Read-onlyIdempotent

One pundit's published NFL record: overall MissedTakes Score, accuracy and sample size, the record broken down by prediction type, and any Pundit of the Week or Month awards. For their election record, call election_pundit. A pundit whose record is in another topic only gets a note saying where it is, never an empty NFL record.

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": {
      "punditSlug": "<punditSlug>"
    },
    "name": "pundit_record"
  }
}

Input Schema

NameRequiredDescriptionDefault
punditSlugYesThe pundit's slug, from find_entities.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description is free to add what they cannot: the contents of the returned record and the non-obvious edge case that a cross-topic pundit yields a redirect note instead of an empty NFL record. That edge-case disclosure is genuinely useful behavior an agent could not infer from structured fields; only a fuller statement of error cases or formatting would raise it further.

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?

Three sentences, front-loaded with what the tool returns, then routing, then the edge case. Every sentence carries distinct information and none restates the title or annotations.

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?

There is no output schema, so the description must explain return values — and it does, listing the metrics, the per-prediction-type breakdown, and awards. Combined with the cross-topic fallback note and the one documented parameter, an agent has everything needed to call this correctly.

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 100% and the single punditSlug parameter already documents its origin ('from find_entities'), so the schema carries the parameter burden. The description adds no syntax, format, or normalization detail beyond that, which is the expected baseline when coverage is complete.

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?

Names a specific resource and scope — one pundit's published NFL record — and enumerates what it contains (MissedTakes Score, accuracy, sample size, breakdown by prediction type, awards). It also explicitly distinguishes itself from election_pundit, so an agent can route without opening either schema.

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?

Provides an explicit alternative with the condition that selects it: 'For their election record, call election_pundit.' It also states what happens when the pundit has no NFL record (a pointer note, not an empty result), removing the main ambiguity about when this tool is the right call.

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