Skip to main content
Glama

futgg_fc27_gg_rating_ranks

Read-only

Get the published FC27 GG-rating rank histograms and return every native role histogram with its source scale and bucket data. Role ids are distinct from card EA item ids, and the response is the publisher's dataset without calculating new player ranks or percentiles. Takes no input.

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

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior4/5

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

Beyond the readOnlyHint and openWorldHint annotations, the description explains that the response contains every native role histogram, includes source scale and bucket data, does not calculate new ranks or percentiles, and takes no input. This adds meaningful behavioral context about the returned dataset and its limitations, though it does not describe pagination or response size.

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?

The description is three focused sentences, front-loaded with the core action and followed by useful scope and limitation details. Every sentence adds value: the role-id distinction, the no-calculation caveat, and the no-input confirmation are all relevant.

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?

For a no-input read-only tool with an output schema, the description is complete enough: it identifies the dataset, the returned histogram structure, the role-id caveat, and the fact that no new ranks or percentiles are computed. The output schema can carry the detailed return shape, so no further description is needed.

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 no input, so there are no parameters whose semantics need explanation; the description confirms this with 'Takes no input.' With zero parameters, the baseline score of 4 is appropriate.

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 description states a specific verb and resource: it gets published FC27 GG-rating rank histograms and returns native role histograms with source scale and bucket data. It also clarifies that role ids differ from card EA item ids, which distinguishes the data scope from related rating tools, though it does not explicitly name a sibling alternative.

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 implied by the phrase 'Get the published FC27 GG-rating rank histograms,' and the exclusion that the response is the publisher's dataset without calculating new player ranks or percentiles helps define when not to use it. However, it does not explicitly say when to choose this over the sibling ratings tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.