Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

futgg_fc27_catalog

Discover FC27 native card catalogs and retrieve catalog IDs, EA IDs, and labels so you can filter players by eaId and avoid confusing internal database IDs.

Instructions

Discover FC27 native card catalogs. Returns native catalog IDs, EA IDs and labels. Use eaId for player filters; internal database IDs are a separate namespace.

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

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.7/5.0

Behavior3/5

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

With no annotations supplied, the description carries the full burden; it does disclose outputs (native catalog IDs, EA IDs, labels) and implies a read-only discovery operation, but never states that it is non-mutating, whether it is paginated, or if any auth/rate constraints apply. It is adequate but thin for a zero-annotation tool.

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 short sentences, front-loaded with the purpose and then the return payload, with the usage caveat last. Nothing is redundant, though "native card catalogs" is a domain term left unexplained and absorbs attention it does not repay.

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?

There is no output schema, so the description's enumeration of returned fields (catalog IDs, EA IDs, labels) is genuinely filling that gap. For a parameterless, annotation-free discovery tool, this covers what an agent needs to call it and interpret the result.

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?

The tool takes no parameters, so the baseline of 4 applies and there is nothing the description could add on that front. The namespace note about internal database IDs versus eaId is useful, though it concerns return values rather than inputs.

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?

Specific verb plus resource: "Discover FC27 native card catalogs," which is a distinct lookup function from the sibling listing tools (players, prices, objectives). It does not name any sibling to contrast against, so an agent still infers the boundary rather than being told it.

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?

"Use eaId for player filters" gives actionable downstream guidance and the namespace warning prevents a wrong-ID mistake when chaining into futgg_fc27_players. However, there is no explicit statement of when to call this tool versus the other FC27 lookups, nor any prerequisite or ordering advice.

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

Deploy Server