Skip to main content
Glama
Sign In
Touchline Wire FPL & Premier League MCP

Touchline Wire FPL & Premier League MCP

Official
by touchlinewire
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

get_transfer_rumours

Read-onlyIdempotent

Retrieve 2026/27 Premier League transfer rumours rated by source reliability, plus club positional needs and incumbent starter benchmarks to evaluate transfer impact.

Instructions

Retrieve 2026/27 Premier League transfer rumours rated Tier 1-4 by source reliability, enriched with club positional depth needs and incumbent starter benchmarks.

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

Input Schema

NameRequiredDescriptionDefault
clubNoOptional club slug (e.g. 'arsenal', 'liverpool', 'spurs')

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description's job is to add data-shape context — which it does by disclosing the season scope, the Tier 1-4 source-reliability rating, and the positional-depth/starter-benchmark enrichment. It does not state result volume, pagination, or whether unfiltered calls return the full rumour set, which keeps it below a 5.

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?

One front-loaded sentence with no filler; the season, competition, resource, and enrichment are all delivered immediately. The trailing 'enriched with...' clause is dense but earns its place by describing returned content.

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 read-only, single-optional-parameter lookup with no output schema, the description covers the essentials: season, resource, reliability tiering, and enrichment fields. Missing only volume/pagination expectations and any acknowledgement of the club filter.

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 coverage is 100% and the single 'club' parameter is already documented with example slugs in the schema. The description never mentions that results can be filtered by club at all, so it adds no meaning beyond the structured field — the baseline 3 applies.

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 names a specific verb and resource ('Retrieve 2026/27 Premier League transfer rumours') and adds qualifying detail about tiering and enrichment, which clearly separates it from siblings like get_fpl_transfer_trends or get_match_preview. It does not explicitly name an alternative, so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

Usage is only implied by the subject matter — an agent can infer this is the tool for transfer speculation rather than FPL trend data or match previews. There is no explicit when-to-use statement, no exclusions, and no mention of when a sibling such as get_fpl_transfer_trends would be preferred.

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