FotMoCP

get_team_season_profile

Retrieve a team's season statistics including table position, expected goals (xG), expected goals against (xGA), expected points, and FIFA ranking by providing the team ID.

Instructions

Get a team's table record, xG, xGA, xPoints, and FIFA ranking 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_season_profile"
  }
}

Input Schema

Name	Required	Description	Default
`teamId`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Jul 15, 2026

TDQS

C2.8/5.0

Behavior2/5

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

The description notes 'when present' for FIFA ranking, hinting at optional fields, but lacks comprehensive behavioral disclosure. No annotations are provided, so the description should cover safety (e.g., read-only nature), permissions, or potential errors, which it does not.

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 that efficiently conveys the tool's output. It avoids redundancy and is front-loaded with the purpose. However, it could be slightly more structured by mentioning the parameter.

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

Completeness3/5

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

Given the low complexity (1 parameter, no output schema), the description lists the returned fields adequately. However, it does not specify the return format (e.g., single object vs. array) or how to interpret metrics like xG or xPoints, which would aid completeness.

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

Parameters2/5

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

The input schema has 0% description coverage, and the description does not mention the 'teamId' parameter or its meaning. Although the parameter name is intuitive, the description fails to add semantic value beyond the schema's type and minimum constraints.

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 'team's season profile', listing specific data fields (table record, xG, xGA, xPoints, FIFA ranking). This distinguishes it from sibling tools like get_team_form and get_team_availability, which focus on different aspects.

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, or when not to use it. For example, it doesn't mention that this tool provides season-level stats as opposed to per-match stats from tools like get_match_stats.

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

Deploy Server