Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

futgg_fc27_gg_ratings

Read-only

Get the complete published FC27 GG-rating dataset and return its native compact rows: wire version, delta-coded EA item ids, positions and scaled scores, with source field order and sentinel values intact. The publication reference refreshes automatically from the source manifest; this is the publisher's dataset, not a locally computed rating. 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_ratings"
  }
}

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

A3.8/5.0
Behavior4/5

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

Beyond readOnlyHint/openWorldHint, the description discloses that the publication reference refreshes automatically from the source manifest (so results can change between calls) and that rows are delta-coded with sentinel values intact, warning that the payload is a wire format rather than clean values. That is meaningful context an agent could not derive from annotations alone.

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 sentences, front-loaded with what is returned and followed by provenance and the no-input note. It is dense with domain jargon (wire version, delta-coded, sentinel values) but every sentence contributes information; nothing is padded.

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?

An output schema exists, yet the description still characterizes the row shape and warns about wire-format encoding, which is appropriate for a zero-parameter dataset dump. The only remaining gap is sibling differentiation, which the description does not address.

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 the baseline is 4; the description's closing "Takes no input" confirms this explicitly and removes any doubt about needing filters or paging arguments.

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 names a specific verb and resource ("Get the complete published FC27 GG-rating dataset") and even enumerates the row contents (wire version, delta-coded EA item ids, positions, scaled scores). It clearly signals a full-dataset dump rather than a filtered view, though it never names the sibling futgg_fc27_gg_rating_ranks or explains how the two differ.

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 rather than stated: "complete published dataset" and "native compact rows" suggest it is the right call when the raw full table is needed, and "not a locally computed rating" clarifies provenance. But there is no explicit when-to-use/when-not guidance and no routing to alternatives such as the ranks tool.

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

All Crawlora MCP toolsInspect
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