Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

futgg_fc27_evolution

Retrieve FC27 evolution details by slug, returning native game, rule, level, and upgrade metadata with raw-definition examples while preserving nulls and source order.

Instructions

Read FC27 evolution detail. Uses the source evolution slug and returns native game/rule/level/upgrade metadata with its published raw-definition example. This differs from list example-card wrappers. Preserves nulls and source order while excluding biography/account/editorial/internal engine data. No previous-edition fallback, player/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

NameRequiredDescriptionDefault
slugYesNative evolution slug from listing; numeric prefix is the site evolution ID, not EA ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.6/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses preservation of nulls and source order, exclusion of biography/account/editorial/internal engine data, and the absence of previous-edition fallback, player/path generation, local upgrades and media execution. It omits permission/auth needs and error behavior for an invalid slug, keeping it short of a 5.

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?

Front-loaded and dense: the read action and return content come first, followed by differentiators and exclusions. The trailing negation list ('media execution', 'internal engine data') is somewhat boilerplate and opaque, but it is compact rather than padded.

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 single-parameter read tool with no output schema, the description does cover return content and important behavioral guarantees. However, without annotations or an output schema it should also state that this is a safe read, and it should describe the error case for a bad slug.

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 slug property already explains that the numeric prefix is the site evolution ID rather than an EA ID. The description only restates that the slug is the 'source evolution slug', adding no format or resolution detail beyond the schema.

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?

States a specific verb and resource ('Read FC27 evolution detail') and scopes the return to native game/rule/level/upgrade metadata plus a raw-definition example. It distinguishes itself against list-style wrappers, though it never names the sibling tool (futgg_fc27_evolutions) explicitly, leaving the list-vs-detail routing partly implicit.

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

Usage Guidelines3/5

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

Usage is only implied: the slug comes 'from listing', which suggests the companion listing tool, and 'No previous-edition fallback' implicitly excludes edition-fallback use cases. There is no explicit when-to-use/when-not framing or named alternative, so the agent must infer the routing.

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