Skip to main content
Glama

Team news

team_news
Read-onlyIdempotent

A Premier League club's injuries, doubts and suspensions as currently reported, with the reason where it is known. Use this for "who is injured at Chelsea?" or "is anyone suspended for Everton?".

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": {
      "club": "<club>"
    },
    "name": "team_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
clubYesA Premier League club, as people write it: "Arsenal", "Spurs", "Man Utd", "Brighton", "Forest".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

Annotations already declare readOnly, non-destructive, idempotent and closed-world behavior, so the safety profile is covered. The description adds a real nuance by saying data is 'as currently reported' and that a reason is included only 'where it is known', signaling freshness volatility and partial records. It does not describe the shape of the returned entries (player, status, reason fields), which is the main remaining gap for a tool with no output schema.

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?

Two sentences, front-loaded with what the tool returns, followed immediately by the natural-language queries that trigger it. Every clause earns its place — the 'reason where it is known' clause conveys a real data caveat rather than filler.

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 single-parameter, read-only lookup with annotations covering safety and no output schema, the description supplies purpose, freshness caveat, and query-level usage. It would be complete with a brief note on what an individual result entry contains (player, injury/doubt/suspension status, reason), but nothing essential to calling it correctly is missing.

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 description coverage is 100% and the single 'club' parameter already documents colloquial accepted forms ('Spurs', 'Man Utd', 'Forest'). The description adds nothing beyond that about the parameter (no guidance on partial names, ambiguity, or error behavior), so 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 concrete resource — a Premier League club's injuries, doubts and suspensions — and a scope qualifier ('as currently reported'). An agent can tell this apart from siblings like club_info, fixtures or table without opening a schema, though the retrieval verb itself is implicit rather than stated.

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?

Two concrete example queries ('who is injured at Chelsea?', 'is anyone suspended for Everton?') give clear positive usage context and cover both injury and suspension intents. There are no explicit exclusions or named alternatives (e.g., pointing to club_info for general club data), so routing is implied rather than fully specified.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources