puntersedge

Sports final scores

sports_results

Read-onlyIdempotent

Final scores from the league's own record for AFL, AFLW, NRL and NRLW, with event_id tying each result to the fixture you hold prices for (null when it could not be matched with certainty). Another sport is refused free of charge. Costs 1 credit. Every plan.

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": {
      "sport_key": "<sport_key>"
    },
    "name": "sports_results"
  }
}

Input Schema

Name	Required	Description
`limit`	No
`season`	No
`sport_key`	Yes	Sport key from sports_list, e.g. afl, nrl, nba or soccer_epl. An unknown key is answered with the valid ones.
`final_only`	No
`competition`	No
`linked_only`	No	Only results tied to a priced fixture, for settling bets.

Output Schema

Name	Required	Description	Default
`data`	Yes	The API response, with links and empty fields removed.

Schema Changelog

Changes observed during successful MCP inspections.

AddedOct 28, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior. The description adds useful context beyond that: credit cost, availability on every plan, rejection of unsupported sports, and null event_id when matching is uncertain. It stops short of auth or rate-limit details.

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?

The description is short, front-loaded, and every sentence carries useful information. The parenthetical and terse cost/plan fragments are efficient rather than wasteful.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema and annotations already cover return shape and safety profile, and the description adds core behavioral context. Still, for a six-parameter tool with low schema coverage, the missing parameter and alternative-tool guidance leaves it only partially complete.

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

Parameters2/5

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

Schema description coverage is only 33%, and the description does not explain limit, season, final_only, or competition. It reinforces supported sport_key values and the event-linking concept, but that is not enough to compensate for the undocumented parameters.

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 description states a specific resource (final scores), the supported competitions (AFL, AFLW, NRL, NRLW), and the key output field event_id. This is enough to distinguish it from odds, race-results, and listing tools without opening the schema.

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?

It gives negative scope (other sports are refused) and cost, which implies when the tool is valid. However, it does not explicitly route the agent between this tool and siblings such as sports_odds, sports_list, or race_results.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All puntersedge tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.