Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

futgg_fc27_players

Search and filter native FC27 player cards by name, position, body type, foot, gender, acceleration, rating, price, and playstyles, with source card and pagination metadata preserved.

Instructions

Search native FC27 player cards. Preserves source card, page/next and capped total metadata. Native definition predicates qualify position/body/foot/gender/acceleration filters; base accelerateType is not a substitute for possible chemistry-style types.

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

NameRequiredDescriptionDefault
footNoComma-separated strong-foot codes:1 right,2 left; OR within selection
nameNoNative player name search text
pageNoNative one-based page
countNoAPI result count bound, 1 to 100
sortsNoSingle native signed key from player-sorts discovery; omit for native GG-rating order
genderNoComma-separated native gender codes:1 male,2 female; OR within selection
club_idNoNative grouped-club eaId from the catalog
league_idNoLeague eaId from the catalog
nation_idNoNation eaId from the catalog
positionsNoComma-separated primary/alternative positions:0,3,5,7,10,12,14,16,18,23,25,27; OR within selection
rarity_idNoRarity eaId from the catalog
weak_footNoComma-separated exact star selections:1,2,3,4,5; OR within selection
body_typesNoComma-separated native body-type codes:1,2,3,4,5,6,7,8,9,10; OR within selection
price__gteNoNative inclusive lower bound: Min Price (console); zero is forwarded unchanged
price__lteNoNative inclusive upper bound: Max Price (console); zero is forwarded unchanged
skill_movesNoComma-separated exact star selections:1,2,3,4,5; OR within selection
overall__gteNoNative inclusive lower bound: Min OVR (console); zero is forwarded unchanged
overall__lteNoNative inclusive upper bound: Max OVR (console); zero is forwarded unchanged
pc_price__gteNoNative inclusive lower bound: Min Price (pc); zero is forwarded unchanged
pc_price__lteNoNative inclusive upper bound: Max Price (pc); zero is forwarded unchanged
accelerate_typesNoComma-separated possible chemistry-style codes:1 explosive,2 lengthy,3 controlled; OR within selection
holographic_typeNoComma-separated native types:1 Regular (holographic),2 Pristine; OR within selection
show_holographicsNoOmit for native Hide mode; true includes holographics,only restricts to holographics
grading_score__gteNoNative inclusive lower bound: Min Item Score (console); zero is forwarded unchanged
grading_score__lteNoNative inclusive upper bound: Max Item Score (console); zero is forwarded unchanged
role_plus_count__gteNoNative inclusive lower bound: Min Roles+ (console); zero is forwarded unchanged
role_plus_count__lteNoNative inclusive upper bound: Max Roles+ (console); zero is forwarded unchanged
playstyles_count__gteNoNative inclusive lower bound: Min PlayStyles (console); zero is forwarded unchanged
playstyles_count__lteNoNative inclusive upper bound: Max PlayStyles (console); zero is forwarded unchanged
number_of_positions__gteNoNative inclusive lower bound: Min Positions (console); zero is forwarded unchanged
number_of_positions__lteNoNative inclusive upper bound: Max Positions (console); zero is forwarded unchanged
role_plus_plus_count__gteNoNative inclusive lower bound: Min Roles++ (console); zero is forwarded unchanged
role_plus_plus_count__lteNoNative inclusive upper bound: Max Roles++ (console); zero is forwarded unchanged
playstyles_plus_count__gteNoNative inclusive lower bound: Min PlayStyles+ (console); zero is forwarded unchanged
playstyles_plus_count__lteNoNative inclusive upper bound: Max PlayStyles+ (console); zero is forwarded unchanged

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description does disclose return-shape context that the agent would otherwise not have: source card preservation, page/next tokens, and a capped total. It stops short of stating that the operation is read-only, how the cap is computed, or the default ordering behavior (the schema carries the GG-rating default instead).

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 sentences, front-loaded with purpose and free of filler. The phrasing is dense and jargon-heavy ('native definition predicates qualify...') but every sentence carries information the agent cannot get from the schema, so nothing is wasted.

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 35-parameter search tool with no annotations and no output schema, the description covers the core operation and return metadata but leaves substantial gaps: no pagination mechanics for page/next, no guidance on how the many range and exclusion filters combine, and no indication of rate limits or result caps beyond the word 'capped'. Adequate but not sufficient for a tool of this complexity.

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 coverage is 100%, so a baseline of 3 applies, but the description earns an extra point by warning that the acceleration filter uses 'native definition predicates' and that the base accelerateType is not equivalent to possible chemistry-style codes. That distinction clarifies an ambiguous enum that the schema alone presents as a plain code list.

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 opening sentence gives a specific verb and resource ('Search native FC27 player cards'), which is unambiguous about what the tool returns. It does not differentiate itself from siblings such as futgg_fc27_player_sorts or futgg_fc27_catalog, but the verb+resource pairing is clear enough that an agent knows this is the card-listing endpoint.

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 explicit guidance on when to use this tool versus alternatives, and no mention that catalog-style ids (club_id, nation_id, league_id, rarity_id) must come from futgg_fc27_catalog, nor that sort keys come from futgg_fc27_player_sorts. The only quasi-guidance is the note that base accelerateType is not a substitute for chemistry-style types, which is a filter caveat rather than a routing rule.

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