Skip to main content
Glama
Crawlora MCP

Crawlora MCP

Official

futgg_fc27_gg_rating_ranks

Fetch FC27 publisher GG-rating rank histograms for every native role, with source scale and bucket data; returns the original dataset without calculating new ranks or percentiles.

Instructions

Get FC27 published GG-rating rank histograms. Returns every native role histogram with source scale and bucket data. Role IDs are distinct from card EA item IDs. This returns the publisher's dataset without calculating new player ranks or percentiles.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful traits: the data is the publisher's raw dataset, it is organized per native role, and it explicitly does not derive ranks or percentiles. It never states read-only status or whether the payload is large/paginated, so the safety and volume profile is left implicit.

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 short sentences, front-loaded with what it returns and then the identity caveat and scope caveat. No filler, no restatement of the name, and each sentence adds a distinct constraint.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-parameter read with no output schema, the description gives enough about the return shape (per-role histograms with source scale and bucket data) and the key limitation. It stops short of describing granularity or size, which matters slightly more given no output schema exists to document the payload.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The note about role IDs versus card EA item IDs is about the data model rather than parameters, but it does help an agent interpret the results correctly.

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?

Specific verb+resource: 'Get FC27 published GG-rating rank histograms', followed by a concrete statement of what is returned ('every native role histogram with source scale and bucket data'). It also rules out a plausible misreading by noting role IDs differ from card EA item IDs, though it never names the sibling futgg_fc27_gg_ratings it most resembles.

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?

The line 'returns the publisher's dataset without calculating new player ranks or percentiles' implicitly tells the agent this is not a computed-rank tool, which is useful routing context. However, there is no explicit when-to-use statement, no named alternative, and no prerequisites or exclusions.

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