Skip to main content
Glama

Results

results
Read-onlyIdempotent

A Premier League club's latest results this season, newest first, in any competition: score, win/draw/loss, extra time and penalty shoot-outs. Default 5, at most 20. Use this for "how did Spurs get on?" or "Newcastle's last five results".

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": {
      "club": "<club>"
    },
    "name": "results"
  }
}

Input Schema

NameRequiredDescriptionDefault
clubYesA Premier League club, as people write it: "Arsenal", "Spurs", "Man Utd", "Brighton", "Forest".
limitNoHow many results, 1 to 20 (default 5).
competitionNoOptional competition filter, as for fixtures.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavioral facts: chronological ordering ('newest first'), season scope, coverage of extra time and penalty shoot-outs, and the default/paging cap. It doesn't say what happens when fewer results exist than requested or whether in-progress matches appear.

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?

Front-loaded with the resource and scope, then the limits, then the example phrasings; no filler sentences. Slightly dense but every clause carries information an agent can act on.

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?

For a three-parameter read tool with full schema coverage and read-only annotations, the definition covers scope, ordering, caps, fields returned, and example asks. Nothing material is missing, and no output schema is needed since the returned fields are enumerated inline.

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%, so all three parameters are already documented, including the 1–20 limit with default 5 — the description's 'Default 5, at most 20' largely repeats that. The one addition is 'in any competition', implying the default is unfiltered, but it never explains the competition parameter's accepted values.

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?

States a specific verb and resource ('a Premier League club's latest results this season') plus scope qualifiers (newest first, any competition) and the exact payload (score, win/draw/loss, extra time, shoot-outs). An agent can distinguish it from 'fixtures' (upcoming), 'next_match' (single future game) and 'live_scores' (in-progress) without opening a 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?

Gives concrete selection context via example utterances ('how did Spurs get on?', 'Newcastle's last five results'), which anchors the past-results use case well. It stops short of an explicit exclusion such as 'not for in-progress matches — use live_scores', so the boundary with the live/fixture siblings is left to inference.

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