Skip to main content
Glama

Club info

club_info
Read-onlyIdempotent

Fixed details for a Premier League club: home ground, nickname, official website and the club's Twenty Clubs pages (fixtures, team news, news, squad, TV, tickets guide, away-day guide, calendar). Use this for "where do Brentford play?" or "what are Ipswich called?".

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

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.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context by labeling the data as 'fixed details' — i.e., a static snapshot, not live data — and by distinguishing between the club's own attributes and the page URLs it returns.

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?

Two tight sentences: the content of the record is front-loaded, then usage examples follow. The long parenthetical list of page names is slightly dense but every item is informative about the payload.

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?

With no output schema, the description usefully enumerates what comes back, and one required parameter plus rich annotations means little else is needed. Minor gap: nothing is said about behavior for an unrecognized or ambiguous club name, which matters for a free-text lookup.

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 schema itself already documents the single club parameter with nickname examples ("Spurs", "Man Utd", "Forest"). The description's argument examples are query-shaped rather than parameter guidance, so it adds little beyond the schema; 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 the resource precisely (a Premier League club) and enumerates the returned fields: home ground, nickname, official website, and links to the club's Twenty Clubs pages. It is clearly a static club-reference tool. The one ambiguity is that it advertises 'fixtures, team news, news, squad' pages while siblings named fixtures and team_news exist, without clarifying that these are links rather than that data.

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?

Concrete example queries ("where do Brentford play?", "what are Ipswich called?") give an agent a clear trigger for this tool. There is no explicit when-not guidance or routing away from fixtures/team_news, so the boundary against siblings is left to inference.

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