Skip to main content
Glama

futgg_fc27_season_pass

Read-only

Get the current native FC27 campaign/Season Pass metadata and return its campaign identity, dates, nullable premium currency metadata and every reward-tier row. Free and premium rows can share a level number and stay separate in source order; isPremium describes a reward tier, not user entitlement. No purchase, account access, reward aggregation, biography or media fetch. Takes no input.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Goes well beyond the readOnlyHint/openWorldHint annotations: it discloses that premium currency metadata is nullable, that free and premium rows may share a level number and must be read in source order, and that isPremium denotes a reward tier rather than user entitlement — a genuinely load-bearing semantic caveat that prevents a misread of the payload.

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?

Three sentences, front-loaded with the resource and return contents, followed by the row-ordering caveat and then scope exclusions. The trailing negative list is slightly listy but each item blocks a plausible misuse, so little is wasted.

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

Completeness5/5

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

With an output schema present and no parameters, the description's remaining job is to explain the tricky parts of the payload — nullability, duplicate level numbers, and the meaning of isPremium — all of which it does. Nothing an agent needs in order to call and interpret this tool correctly is missing.

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

Parameters4/5

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

Zero parameters, so the baseline is 4; the description confirms this explicitly with 'Takes no input,' removing any doubt about passing campaign IDs or filters. There is nothing further to disambiguate.

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?

States a specific verb ('Get') and resource ('current native FC27 campaign/Season Pass metadata') and enumerates exactly what comes back: campaign identity, dates, nullable premium currency metadata, and every reward-tier row. The negative scope clause ('No purchase, account access, reward aggregation, biography or media fetch') fences off adjacent capabilities so an agent can tell this apart from catalog/definition-style siblings.

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 'current native' framing plus the explicit exclusion list make it clear this is the read path for season-pass structure, not for purchasing or entitlement checks. No sibling tool is named as an alternative, so the agent must infer routing from sibling names rather than being told.

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.