Crawlora MCP

futgg_fc27_players

Read-only

Search native FC27 player cards and return the source cards plus native next, currentPage and total metadata. Filters are single qualified native values: nation_id, league_id, club_id and rarity_id are catalog eaIds from futgg_fc27_catalog (concept rarity ids can be negative, for example -9991; club ids are native grouped clubs, so sibling variants can share results), while positions, foot, gender, body_types and accelerate_types are the closed native code sets. When a definition predicate is used, every returned card is joined against its native definition, so acceleration requires a nonempty chemistry-style accelerateTypes array and an evolution item is rejected under that selector. page is the source's own one-based page (default 1) and count is this API's 1-to-100 result bound (default 3). total can be capped at 10,000 and a valid filter can return an empty native list; no attribute, ranking or chemistry outcome is computed locally.

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_players"
  }
}

Input Schema

Name	Required	Description
`foot`	No	Optional preferred foot: 1 right, 2 left.
`page`	No	Optional native one-based page, defaults to 1.
`count`	No	Optional result count bound from 1 to 100, defaults to 3. This is this API's bound, not a claim about the upstream's maximum accepted page size.
`gender`	No	Optional card gender: 1 male, 2 female.
`club_id`	No	Optional native grouped-club eaId from the FC27 catalog. A group is not a unique club: sister or sibling variants can share the same result set, and unique_club_id is not accepted.
`league_id`	No	Optional league eaId from the FC27 catalog (futgg_fc27_catalog). Use the catalog eaId, never its internal id.
`nation_id`	No	Optional nation eaId from the FC27 catalog (futgg_fc27_catalog). Use the catalog eaId, never its internal id.
`positions`	No	Optional native position code: 0 GK, 3 RB, 5 CB, 7 LB, 10 CDM, 12 RM, 14 CM, 16 LM, 18 CAM, 23 RW, 25 ST, 27 LW. Alternate positions count as a match, and 0 is a real GK filter.
`rarity_id`	No	Optional rarity eaId from the FC27 catalog. Native concept rarity EA IDs can be negative (for example -9991, -9992 and -9993); those are valid catalog values, not malformed card-item identifiers.
`body_types`	No	Optional native body-type code: 1 Lean Medium, 2 Average Medium, 3 Stocky Medium, 4 Lean Tall, 5 Average Tall, 6 Stocky Tall, 7 Lean Short, 8 Average Short, 9 Stocky Short, 10 Unique.
`accelerate_types`	No	Optional native acceleration type: 1 Explosive, 2 Lengthy, 3 Controlled. The match requires a nonempty native chemistry-style accelerateTypes array, not the base accelerateType, and an evolution item under this selector is rejected because it uses a different source predicate.

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 readOnlyHint and openWorldHint annotations, the description discloses pagination behavior, the 1-to-100 count bound, the 10,000 total cap, possible empty results, definition-join filtering, evolution rejection under acceleration selectors, and that no local attribute or chemistry computation occurs.

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?

The description is front-loaded with the core purpose and then proceeds through filters, predicate behavior, pagination, and edge cases. It is dense but mostly earns its length, with only minor redundancy against the already detailed input schema.

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?

Given 11 optional parameters, rich schema descriptions, annotations, and an output schema, the definition covers the operational essentials: valid filter sources, pagination defaults, result bounds, empty-result possibility, and definition-specific filtering behavior.

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?

Schema description coverage is 100%, so the baseline is already high. The description adds cross-parameter meaning, especially the distinction between catalog eaIds, grouped club IDs, negative concept rarity IDs, and definition-predicate join behavior, though some of this overlaps with the detailed schema descriptions.

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?

The description states a specific verb and resource: search native FC27 player cards and return the source cards plus native metadata. It distinguishes the tool from related catalog/definition tools by explaining that catalog eaIds are inputs and that definition predicates trigger native definition joins.

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?

It gives clear usage context: filters must be qualified native values from futgg_fc27_catalog, and definition selectors impose additional join semantics. It does not explicitly compare this search tool against alternatives like futgg_fc27_definitions or futgg_fc27_player_sorts, but the operational guidance is strong.

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.