Crawlora MCP

futgg_fc27_manager

Read-only

Get one FC27 manager item and return professional identity, native nation/default league and public market observations. Pass a positive manager ID from futgg_fc27_managers; EA player IDs and facet queryValue selectors are different namespaces. Biography and portrait data are excluded.

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": {
      "id": "<id>"
    },
    "name": "futgg_fc27_manager"
  }
}

Input Schema

Name	Required	Description	Default
`id`	Yes	Required positive native manager item ID from futgg_fc27_managers, distinct from EA card IDs and nation/league selectors.

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 13, 2026

TDQS

A4.1/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds a genuinely useful scope exclusion (biography and portrait data are not returned), which stops an agent from expecting artwork fields. Beyond that it says nothing about market-observation freshness, rate limits, or failure modes for invalid IDs.

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

Conciseness5/5

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

Three sentences, zero filler: what it returns comes first, ID provenance and namespace warnings second, exclusions last. Every clause carries information an agent needs before calling.

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?

With an output schema present, return structure needn't be explained, and the description still names the returned data categories and the excluded ones. Together with annotations and full schema coverage, nothing an agent needs to invoke this correctly is missing.

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 description largely restates the schema's own wording (positive native manager ID from futgg_fc27_managers, distinct from EA card IDs and selectors). The namespace disambiguation is valuable but already duplicated in the parameter description, so the definition adds little new meaning beyond structured fields.

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?

States a specific verb and resource ("Get one FC27 manager item") plus the returned facets (identity, nation/default league, market observations). The singular "one item" implicitly separates it from the plural futgg_fc27_managers list tool, and the description is unmistakably about a single-entity lookup.

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?

Tells the agent where the ID must come from (futgg_fc27_managers) and warns that EA player IDs and facet queryValue selectors are separate namespaces, which prevents a common mis-call. It stops short of an explicit when-not-to-use clause or naming a sibling to prefer for aggregate/filtered queries.

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.

Resources

Need Help?