Skip to main content
Glama
Sign In
FotMoCP

FotMoCP

by Margeshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_match_stats

Retrieve the score and deduplicated team and player stats for a football match using a match ID or FotMob URL.

Instructions

Get the score plus deduplicated team and player stats. matchId may be an ID or FotMob URL.

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": {
      "matchId": "<matchId>"
    },
    "name": "get_match_stats"
  }
}

Input Schema

NameRequiredDescriptionDefault
matchIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations, the description fails to disclose behavioral traits like side effects, authentication needs, or return structure. It only mentions what is returned (score, deduplicated stats) without details on deduplication behavior.

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 description is a single sentence, concise and front-loaded. It wastes no words, but could benefit from slight structuring (e.g., separate parameter note).

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (1 param, no output schema, no annotations), the description is minimal. It does not explain the return format or how deduplication works, which is important for a stats tool among many siblings.

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 0%, but the description adds useful context for matchId: it can be an ID or FotMob URL. This supplements the schema's type constraints. However, no other parameter details are provided.

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 clearly states the tool retrieves 'score plus deduplicated team and player stats', specifying a concrete verb and resource. However, it does not explicitly differentiate from sibling tools like get_goalkeeper_match_stats or get_match_prediction_context.

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?

No guidance on when to use this tool versus alternatives. The only usage hint is that matchId can be an ID or URL, which is more of a parameter note than a usage guideline.

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

Deploy Server

Other Tools