Skip to main content
Glama
Sign In
FPL MCP

FPL MCP

by MoayadAbbara
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

substitute

Swap a bench player into the starting lineup and move a starter to the bench. Specify the bench player and starter to replace; team ID is optional.

Instructions

Swap a bench player into the starting XI and move a starter to the bench.

    Args:
        bench_in: Name of the bench player to bring into the XI.
        starter_out: Name of the starting player to move to the bench.
        team_id: Optional; detected from your account if omitted.

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": {
      "bench_in": "<bench_in>",
      "starter_out": "<starter_out>"
    },
    "name": "substitute"
  }
}

Input Schema

NameRequiredDescriptionDefault
team_idNo
bench_inYes
starter_outYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior3/5

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

With no annotations provided, the description alone carries the burden of behavioral disclosure. It accurately describes the swap action but does not mention side effects, reversibility, permission requirements, or any validation rules. It is neither misleading nor misleading, but lacks extra detail such as whether the change affects the current or future gameweeks.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is succinct and well-structured: one clear sentence for the main action followed by an efficiently formatted Args section. Every word adds value, and the most critical information (what the tool does) is front-loaded.

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

Completeness4/5

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

For a simple swap operation with an output schema present, the description covers the essential action and parameters. It could add notes on edge cases (e.g., if the player is already in the XI) but is otherwise complete for an agent to invoke the tool correctly.

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

Parameters5/5

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

Schema coverage is 0%, but the description's Args block thoroughly explains each parameter, including the optional team_id. It fully compensates for the schema's lack of metadata, ensuring agents understand the purpose and expected values.

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 tool's function: 'Swap a bench player into the starting XI and move a starter to the bench.' This specific verb+resource formulation distinguishes it from siblings like make_transfer, set_captain, etc., with no ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use the tool—whenever a player substitution is needed—without explicitly naming alternatives or exclusions. While it doesn't reference sibling tools like make_transfer, the distinct purpose and parameter names make the intended use obvious.

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