Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

futgg_fc27_prices

Retrieve FC27 published card prices across Console and PC standard or dynamic publications, returning native compact price and status fields without estimates.

Instructions

Get FC27 published card prices. Supports all four native Console/PC standard/dynamic publications. Dynamic columns are combined with the same publication's shared index exactly as the website does; every price/status column is checked against its item index. Returns native compact fields, not computed price estimates or history.

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

Input Schema

NameRequiredDescriptionDefault
datasetNoNative publication key; ps5 is the website's Console dataset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.7/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 substantial work: it discloses the join semantics (dynamic columns combined with the same publication's shared index), the validation behavior (every price/status column checked against its item index), and explicitly what is NOT returned (computed estimates, history). Gaps remain around what happens when the optional dataset is omitted and whether responses are paginated.

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 tight sentences, front-loaded with the core purpose, with no filler. Terms like "shared index" and "item index" are used without definition, which slightly raises parsing cost for an agent unfamiliar with the domain.

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 single-optional-parameter read tool with no output schema and no annotations, the description covers what the tool returns at a high level and what it deliberately excludes. The one missing piece is behavior when dataset is absent, which a caller would need to know.

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 enum parameter is already fully documented, so the baseline applies. The description does add a little semantic meaning by explaining that the four values cover Console/PC in standard and dynamic flavors and that dynamic publications are index-joined, but it does not state a default when the parameter is omitted.

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 ("Get FC27 published card prices") and scopes it to native published data rather than derived values. The closing clause distinguishes it from computed/index or historical tools such as an evolution or price-index sibling, though it does so by exclusion rather than naming them.

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: "not computed price estimates or history" tells the agent this is not the historical or derived tool, which is useful routing signal. But it never says explicitly when to pick this versus the price-index or evolution siblings, and gives no preconditions or fallback guidance.

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