Crawlora MCP

futgg_fc27_catalog

Read-only

Get the published FC27 card catalog and return its native groups: clubs, nations, leagues, rarities and the source role metadata, with each row's internal id and its EA id. Nation, league, club and rarity filters take eaId from this catalog. Campaign inclusion/exclusion uses native campaign-squad id from futgg_fc27_campaign_squads instead. Native concept rarity EA IDs can be negative (for example -9991). The catalog follows the source's rotating published asset through its own manifest and is cached five minutes per process; this is explicitly the FC27 edition, and no account, purchase or unqualified filter is exposed. 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_catalog"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 11, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses caching behavior (five minutes per process), that the underlying asset rotates and is resolved via the source's own manifest, that no account or purchase is involved, and a real data quirk (concept rarity EA IDs can be negative, e.g. -9991). These are the kind of operational details an agent cannot infer from structured fields.

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?

Front-loaded with what is returned, then follows with the constraints an agent needs before calling. Dense but nearly every clause earns its place; 'Takes no input' is mildly redundant against the empty schema and the final negative-ID example adds a touch of detail at the end.

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?

An output schema exists, yet the description still names the payload groups and the id pair (internal id plus EA id) an agent will need for joins, and annotations cover the safety profile. Freshness, source behavior, and cross-tool id provenance are all covered, leaving no substantive gap for a zero-parameter lookup tool.

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?

With zero parameters, the baseline applies; the description correctly notes 'Takes no input', matching the empty schema. The eaId discussion is about how other tools' parameters should be sourced, which is helpful cross-tool semantics but not this tool's own parameter documentation.

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 and resource ('Get the published FC27 card catalog') and immediately enumerates the returned native groups (clubs, nations, leagues, rarities, role metadata) with row identifiers. The 'FC27 edition' scoping and the explicit note that campaign data lives in a different tool separate it cleanly from any generic catalog sibling.

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?

Gives actionable routing context: nation/league/club/rarity filters elsewhere must take their eaId from this catalog, while campaign inclusion/exclusion must instead use the native campaign-squad id from futgg_fc27_campaign_squads. That is clear when-to-use guidance, though it frames usage indirectly through filter consumers rather than saying outright 'call this first to resolve eaIds'.

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

All Crawlora MCP tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?