Skip to main content
Glama

Footalytics

list_results

Settled official predictions with the real score and the grade — hit/miss per market and Brier score; the public accuracy record (1 credit per successful call).

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

Input Schema

NameRequiredDescriptionDefault
teamNoTeam name in English, e.g. Arsenal. Chinese names do not resolve.
limitNoOptional, default 10, max 20
leagueNoLeague filter (eng.1 or premier-league)
fixtureNoSingle fixture id

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses that only settled (not pending) records are returned, describes the shape of each record (score, grade, hit/miss, Brier), and states the cost model of 1 credit per successful call. It omits pagination/ordering behavior and any auth or error conditions, which keeps it below a 5.

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?

A single dense sentence that front-loads the core identity ('settled official predictions') and then the output payload. Every clause carries information, though the em-dash packing of grade, hit/miss, Brier score, and credit cost makes it slightly dense to scan.

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?

There is no output schema, so the description must convey return contents, and it does so concretely (score, grade, hit/miss, Brier). Credit cost is a useful addition for an agent planning calls. Minor gaps remain around pagination defaults and result ordering for a 4-optional-parameter list 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 description coverage is 100%, so team, league, fixture, and limit are already fully documented with examples and constraints in the schema. The description adds no filtering semantics beyond what the schema states, so the baseline of 3 applies.

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 names the specific resource — settled official predictions — and enumerates what comes back (real score, hit/miss per market, Brier score), which is clearly distinct from an unsettled-prediction sibling like get_match_prediction. It stops short of an explicit verb, relying on the tool name 'list_results' to supply it.

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?

The phrase 'the public accuracy record' implies the use case (reviewing past performance), and 'settled' implicitly excludes pending fixtures. However, there is no explicit statement of when to choose this over get_match_prediction or how to combine it with list_fixtures, so routing 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