SportScore

get_matches

List live and recent matches for a sport. Returns up to limit matches with scores, status, kickoff time and team logos. Good default for 'what's happening in football right now?'.

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": "<sport>"
    },
    "name": "get_matches"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`sport`	Yes	Sport to query. One of football, basketball, cricket, tennis.

Schema Changelog

Changes observed during successful MCP inspections.

First observedApr 23, 2026

TDQS

A4/5.0

Behavior3/5

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

No annotations provided, so description carries burden. Mentions returned fields (scores, status, kickoff time, logos) and limit. Does not clarify what 'recent' means, if future matches are included, or ordering.

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?

Two sentences, no unnecessary words. Front-loaded with action and returns. Second sentence adds a practical use case. Highly efficient.

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?

No output schema, but description lists return fields. Lacks response structure details and error handling. For a simple list tool, it's nearly complete. Low complexity (2 params) helps.

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 50% (only sport has description). Description adds 'Returns up to limit matches', explaining limit's effect, but no detail on default or max/min beyond schema defaults. Baseline 3 with partial compensation.

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?

Description clearly states the verb 'list', resource 'matches', and scope 'live and recent for a sport'. It distinguishes from siblings like get_match_detail (single match) and get_bracket (tournament).

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?

Provides a clear use case: 'Good default for what's happening in football right now?', implying it's for overview. However, lacks explicit when-not-to-use or alternative tool names, though sibling context exists.

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

All SportScore 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.

Resources

Need Help?