Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

futgg_fc27_definitions

Retrieve FC27 card definitions by comma-separated EA item IDs, preserving card identity and stat fields from source batch metadata.

Instructions

Get native FC27 card definitions. Reads the source batch metadata endpoint with EA item IDs and preserves card identity/stat fields. This does not fetch accounts or install anything.

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

NameRequiredDescriptionDefault
idsYesComma-separated EA item IDs, 1 to 100

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral burden; it does establish that this is a read against a source batch endpoint and that card identity/stat fields are preserved, which implies a read-only, non-destructive operation. However, it says nothing about behavior on unknown or partial EA item IDs, error handling, or the batching limit's effect, so the disclosure is partial.

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 with the core action front-loaded and no padding in the first two. The closing sentence about accounts and installation is largely wasted space, keeping it below a 5.

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

Completeness3/5

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

For a one-parameter batch lookup with no output schema, the description gives a rough idea of the returned data (card identity/stat fields) but leaves the actual response shape, behavior on missing IDs, and result ordering unspecified. It is adequate but has clear gaps for an agent that needs to consume the output.

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 already documents the single parameter as 'Comma-separated EA item IDs, 1 to 100'. The description only echoes 'with EA item IDs' and adds no syntax, format, or validation meaning beyond the schema, so the 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 opens with a specific verb and resource ('Get native FC27 card definitions') and adds that it reads the source batch metadata endpoint keyed by EA item IDs, which is enough to distinguish it from the catalog/players siblings in broad terms. It never names a sibling explicitly, so the differentiation is inferential rather than stated.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no statement of when to use this versus futgg_fc27_players or futgg_fc27_catalog, which are the obvious alternatives for card data. The only exclusion offered ('does not fetch accounts or install anything') addresses concerns an agent would not plausibly have, so it provides no real routing guidance.

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

Deploy Server

Other Tools