Skip to main content
Glama
Sign In
FotMoCP

FotMoCP

by Margeshy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

get_player_workload

Retrieve a player's recent minutes, last appearance, and injury status to assess their workload.

Instructions

Get a player's recent minutes, last appearance, and injury status.

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": {
      "playerId": "<playerId>"
    },
    "name": "get_player_workload"
  }
}

Input Schema

NameRequiredDescriptionDefault
playerIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only lists the data returned (minutes, appearance, injury status) but fails to state that the tool is read-only, does not specify data freshness or time range for 'recent,' and omits any potential side effects or authentication requirements.

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, efficient sentence with no filler. It front-loads the core action and data, making it easy to scan.

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 tool has one parameter, no output schema, and no annotations, the description is too brief. It fails to specify the output structure, time range for data, or how 'recent' is defined, leaving the agent with insufficient context to use the tool effectively.

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 sole parameter playerId is described only by name in the schema; the description does not add any additional meaning, such as how to obtain the playerId or its format. Since schema description coverage is 0%, the description should compensate but does not.

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 a player's recent minutes, last appearance, and injury status, giving a specific verb and resource. However, it does not distinguish this tool from siblings like get_team_availability or get_match_stats, which could also involve player data.

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 explicit guidance on when to use this tool versus alternatives or prerequisites. The description implies it's for player workload info, but lacks context on when not to use it or what other tools might be better suited (e.g., for match-specific stats).

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