Skip to main content
Glama

tactica. football intelligence

Get a match forecast

get_match_forecast
Read-onlyIdempotent

Home, draw and away chances and expected goals for one fixture. Paid: 0.25 USDC per call via x402 on Base.

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": {
      "fixtureId": "<fixtureId>"
    },
    "name": "get_match_forecast"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixtureIdYestactica. fixture id, from list_fixtures

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds important payment context (0.25 USDC per call via x402 on Base), which is useful behavioral information beyond annotations, but it does not explain payment failure handling or rate limits.

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, front-loaded with the returned forecast values and followed by the payment requirement. There is no unnecessary wording.

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?

For a low-complexity, single-parameter read tool, the description names the return values and the payment cost. With no output schema, it could say slightly more about output shape, but it is complete enough for correct invocation.

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 fixtureId is documented as coming from list_fixtures. The description adds only the phrase 'for one fixture' and no additional syntax or semantic detail beyond the schema, so baseline 3 is appropriate.

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?

States the specific outputs (home/draw/away chances and expected goals) and scope (one fixture), so the resource is clear. It does not explicitly distinguish itself from sibling forecast or picks tools, so it falls short of a 5.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description only gives scope ('for one fixture') and the schema notes the fixture id comes from list_fixtures. It provides no explicit when-to-use guidance versus alternatives such as get_betting_picks, and no exclusions.

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