Skip to main content
Glama

tactica. football intelligence

Get a match Case File

get_case_file
Read-onlyIdempotent

The full tactica. Case File for one fixture: forecast, score grid, evidence and what drove the forecast. Paid: 1.00 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_case_file"
  }
}

Input Schema

NameRequiredDescriptionDefault
fixtureIdYestactica. fixture id, from list_fixtures

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, closed-world and non-destructive, so the safety profile is covered. The description adds genuinely non-obvious behavior: each call costs 1.00 USDC via x402 on Base, which materially affects agent invocation strategy. It stops short of explaining payment flow mechanics or failure behavior when payment is missing.

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 tight sentences with the payload enumerated up front and the cost constraint placed last. Zero filler, and the most decision-relevant facts (scope and price) lead and close.

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?

With no output schema, the description does the work of describing returns by naming forecast, score grid, evidence, and drivers, and it discloses the pricing model. It is nearly complete for a single-parameter read tool; only edge cases like missing forecasts for a fixture are unaddressed.

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 the fixtureId property already documents its pattern and that it comes from list_fixtures. The description only restates 'for one fixture', adding no syntax, formatting, or sourcing detail beyond the schema. 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 a specific verb and resource ('full tactica. Case File for one fixture') and enumerates the payload contents: forecast, score grid, evidence, and forecast drivers. The word 'full' implies a superset of the narrower siblings like get_match_forecast, but it does not name an alternative explicitly, so the sibling differentiation is inferred rather than stated.

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?

Usage is only implied: 'full' suggests this is the comprehensive option versus narrower sibling endpoints, but there is no explicit when-to-use, when-not-to-use, or 'prefer X if you only need the forecast' guidance. The payment note tells the agent the cost but not the decision rule.

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