Crawlora MCP

futgg_fc27_evolution

Read-only

Read one native FC27 evolution by its source slug and return its game/rule/level/upgrade metadata with the published raw-definition player example, preserving nulls and source order. Take the slug from futgg_fc27_evolutions; the numeric prefix is the site evolution id, not an EA id. No previous-edition fallback, player or path generation, local upgrades or media execution.

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": {
      "slug": "<slug>"
    },
    "name": "futgg_fc27_evolution"
  }
}

Input Schema

Name	Required	Description	Default
`slug`	Yes	Required native evolution slug from the listing; the numeric prefix is the site evolution id, not an EA id.

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.2/5.0

Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral detail beyond them — nulls and source order are preserved, no previous-edition fallback occurs, and the numeric prefix is a site evolution id rather than an EA id. It does not discuss error behavior for unknown slugs, but the added context is well above what the annotations carry.

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 dense sentences, front-loaded with purpose and followed by parameter provenance then exclusions; nothing is padding. Phrasing is slightly compressed ('with the published raw-definition player example'), but each clause carries information.

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 one required parameter, full schema coverage, an output schema covering return values, and read-only annotations, the description supplies everything else an agent needs: payload contents, slug provenance, id semantics, and explicit non-capabilities.

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 single slug parameter is already documented as coming from the listing with the numeric-prefix caveat, so the description largely restates the schema. It adds no format, length, or validation detail beyond that, warranting the baseline 3.

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 ('Read one native FC27 evolution by its source slug') and enumerates the payload (game/rule/level/upgrade metadata plus the raw-definition player example). It also implicitly separates itself from the sibling listing tool futgg_fc27_evolutions by describing single-record retrieval keyed on a slug that the listing supplies.

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 slug must come from ('Take the slug from futgg_fc27_evolutions') and explicitly excludes adjacent capabilities ('No previous-edition fallback, player or path generation, local upgrades or media execution'). It stops short of naming a specific sibling to use for those excluded needs, so routing beyond the slug source is left to inference.

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.