Crawlora MCP

futgg_fc27_definitions

Read-only

Get native FC27 card definitions for a batch of EA item definition IDs in one upstream read, preserving each card's identity and stat fields. ids is 1 to 100 positive EA item definition IDs (not internal row ids, and not necessarily base athlete ids); the native batch length follows the requested array. Native paging can be null and total can be 0 even when definitions are returned, so membership is the returned data array, not those fields. Biological identity fields are outside this game-card contract.

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": {
      "ids": "<ids>"
    },
    "name": "futgg_fc27_definitions"
  }
}

Input Schema

Name	Required	Description	Default
`ids`	Yes	Required 1 to 100 EA item definition IDs, each positive. These are card definition EA ids, not the catalog's internal row ids and not necessarily base athlete ids; the native batch length follows the array length.

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

A3.6/5.0

Behavior4/5

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

Beyond the readOnlyHint/openWorldHint annotations, the description discloses a real upstream quirk: paging can be null and total can be 0 even when definitions are returned, so membership must be read from the data array. It also bounds scope by excluding biological identity fields, which prevents misuse of the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The text is front-loaded and reasonably tight, but it repeats itself: 'not internal row ids' and 'batch length follows the array' appear in both the description and the schema wording, and the closing biological-identity sentence is cryptic without context.

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 a single required parameter, an output schema, and read-only annotations, the definition covers what an agent needs: input identity constraints, batch bounds, and the response-envelope caveat. Only the absence of sibling routing keeps it from being fully complete.

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%, so the parameter is already documented; the description largely restates the same semantics (1-100 positive EA item definition ids, not internal row ids, batch length follows the array) rather than adding new syntax or format detail. Baseline 3 applies when the schema does the heavy lifting.

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 opens with a specific verb and resource: 'Get native FC27 card definitions for a batch of EA item definition IDs in one upstream read,' plus the retention of identity/stat fields. It is clear what the tool returns, though it does not name a sibling alternative such as catalog or players lookups.

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?

Usage is only implied: the ids must be EA item definition ids, which tells an agent when this tool is the right input contract. There is no explicit when-to-use/when-not-to-use statement or routing to a sibling tool such as the catalog for internal row ids.

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.