Skip to main content
Glama

Sportmonks Football (Unofficial)

Sportmonks Livescores

sportmonks_livescores
Read-onlyIdempotent

Live in-play soccer matches now, current minute, state, teams, and running score. Example: sportmonks_livescores({ _apiKey: "your-token" })

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "_apiKey": "your-sportmonks-api-key"
    },
    "name": "sportmonks_livescores"
  }
}

Input Schema

NameRequiredDescriptionDefault
_apiKeyYesSportmonks API token (get one at my.sportmonks.com; free plan = Danish/Scottish leagues)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety and idempotency profile is covered structurally. The description adds the useful behavioral fact that results reflect current in-play state (minute, running score), but says nothing about refresh cadence, staleness, rate limits, or coverage limitations — the schema's free-plan note about Danish/Scottish leagues is the only scope signal.

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

Conciseness4/5

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

The first sentence is dense and front-loaded, listing exactly what comes back, which is the right thing to lead with. The trailing example call duplicates the schema's examples block and earns little, keeping it short of a 5.

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 one-parameter, read-only, no-output-schema tool, the description covers the essential unknown — what fields the response contains — which is exactly what an absent output schema leaves open. It stops short of describing the response envelope or volume of matches returned, but nothing required to call it correctly is missing.

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?

With a single parameter and 100% schema description coverage, the schema already documents _apiKey fully, including where to obtain it and the free-plan restriction. The description's inline example merely restates the schema's own example object, adding no new meaning about the parameter.

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 names the resource precisely — live in-play soccer matches — and enumerates the payload (minute, state, teams, running score), which is clearer than a bare verb+noun. It does not explicitly contrast with siblings like sportmonks_fixture or sportmonks_fixtures_by_date, though the 'live in-play ... now' framing does most of the differentiating work.

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: the word 'now' and 'live in-play' suggest this is the tool for real-time state rather than historical or scheduled fixtures. There is no explicit statement of when to prefer it over sportmonks_fixtures_by_date or sportmonks_fixture, and no exclusions or prerequisites beyond the schema's token note.

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.