FotMoCP

get_team_form

Retrieve a team's recent results including home/away splits, ranking, and expected goals (xG) per match.

Instructions

Get recent results and home/away splits, with ranking and per-match xG when present.

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": {
      "teamId": "<teamId>"
    },
    "name": "get_team_form"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No
`teamId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

C2.7/5.0

Behavior3/5

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

With no annotations, the description bears the full burden of disclosure. It mentions that the tool returns results, home/away splits, ranking, and xG, implying a read-only operation. However, it does not describe ordering, pagination behavior, or what 'when present' means for xG, leaving some ambiguity.

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 a single sentence that packs information efficiently. However, it could be restructured to list key outputs and parameters more clearly. It is concise but not optimally structured for quick parsing.

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?

The tool has low complexity (2 parameters, no output schema), yet the description does not fully explain the output format or behavior. Terms like 'home/away splits' and 'ranking' are left undefined, and without output schema, the agent has insufficient detail to expect the result structure.

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

Parameters1/5

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

The description does not reference either parameter (teamId, limit). Given 0% schema description coverage, the description fails to compensate, leaving the agent without guidance on how to specify the team or control the number of results.

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 verb 'Get' and the resource 'recent results and home/away splits, with ranking and per-match xG when present.' It distinguishes the tool's purpose somewhat from siblings like 'get_team_season_profile' by focusing on recent form, but could be more specific about the exact output scope.

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 provides no guidance on when to use this tool versus alternatives such as 'get_team_season_profile' or 'find_matches.' There is no mention of prerequisites or contextual scenarios, relying solely on the tool name for context.

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

Deploy Server