Skip to main content
Glama

tactica. football intelligence

List upcoming fixtures

list_fixtures
Read-onlyIdempotent

Upcoming fixtures tactica. covers, with fixture ids, kick-off times, teams and league. Free.

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_fixtures"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare read-only, idempotent, non-destructive, and closed-world behavior. The description adds useful return-content detail and cost information ('Free'), but it does not describe ordering, pagination, limits, or freshness for the fixture list. With annotations covering safety, this is adequate but incomplete.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short, but it is written as broken fragments rather than clear sentences. 'Upcoming fixtures tactica. covers' is ambiguous and slows comprehension. 'Free' is useful but placed as an afterthought.

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 simple, zero-parameter, read-only listing tool, the description covers what is returned and that access is free. Safety behavior is already covered by annotations. Ordering and result-size behavior are not stated, but the low complexity keeps this close to complete.

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

Parameters4/5

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

The tool takes zero parameters, so there is no parameter meaning to document. The baseline for zero-parameter tools is 4, and nothing in the description contradicts the empty schema.

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 identifies the resource as upcoming fixtures and names the fields returned: fixture ids, kick-off times, teams, and league. The verb is only implied and the phrase 'tactica. covers' is garbled, but the core purpose is still clear. It does not explicitly distinguish itself from sibling tools such as forecasts or betting picks.

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?

There is no explicit guidance on when to use this tool versus alternatives. The single word 'Free' gives pricing context but not usage direction. No exclusions or prerequisites are stated.

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