FC 26 MCP

by INSANE0777

Overview Schema Source Related Servers Discussions Admin

Python

Local

le_list_team_players

Retrieve all players from a specific team by providing the team ID or name.

Instructions

List all players in a club/team.

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": "le_list_team_players"
  }
}

Input Schema

Name	Required	Description	Default
`team`	No	Team name (if ID not provided).
`teamid`	No	Team ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.29Jul 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

With no annotations, the description must fully disclose behavior, but it omits what happens when both or neither parameter is provided, and does not specify the return format (e.g., list of player names or IDs).

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?

Single sentence, front-loaded with the essential action. While concise, it could benefit from slightly more detail without becoming verbose.

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 no output schema, so the description should convey what is returned (e.g., list of player names or full player objects). It also fails to explain the interplay between 'team' and 'teamid' parameters.

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 covers all parameters with descriptions; the description adds no extra meaning beyond 'List all players in a club/team'. Baseline score of 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'list' and the resource 'players in a club/team', which is specific and distinct from sibling tools like le_search_players (which implies filtering) and le_get_db_rows (generic).

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, no prerequisites or conditions stated, and no advice on choosing between 'team' and 'teamid' parameters.

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