Crawlora MCP

futgg_fc27_managers

Read-only

List native FC27 manager items and return source pages, identities and market observations. Use manager facet queryValue selectors, preserving explicit zero/omission for league and price controls; platform, quality, extinction, search and native pagination are optional. No prices or league assignments are calculated.

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

Input Schema

Name	Required	Description
`q`	No	Optional native manager name search, at most 100 characters.
`page`	No	Optional positive native page. Preserve the source's out-of-range404 behavior.
`league`	No	Optional league queryValue from manager facets. Zero is the native unresolved-league selection, not omission.
`nation`	No	Optional nation queryValue from futgg_fc27_manager_facets.
`extinct`	No	Optional native extinction selector: all, only or hide.
`quality`	No	Optional native quality: all, bronze, silver or gold.
`platform`	No	Optional native platform ps5 or pc; omit for the source default.
`max_price`	No	Optional inclusive maximum source price.
`min_price`	No	Optional inclusive minimum source price. Zero is explicit and affects unpriced records.
`page_size`	No	Optional native page size from 1 through 96.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 13, 2026

TDQS

B3.4/5.0

Behavior3/5

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

With readOnlyHint and openWorldHint already declared, the description usefully adds that no prices or league assignments are computed and that source paging is preserved. It leaves out how many records a page returns in practice, what happens at the end of the result set, and how volatile the upstream market observations are for an open-world source.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded and only three sentences, with the key scope statement first. The middle sentence, however, is a dense run of jargon ('preserving explicit zero/omission') and spends a clause merely repeating that every parameter is optional, which the schema already makes obvious.

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?

Output schema exists, so return values needn't be spelled out, but phrases like 'market observations' are left unexplained for a 10-parameter filtering tool. An agent gets enough to call it, but not a confident picture of what a page of results yields or how deep the native pagination goes.

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?

Schema description coverage is 100%, so a 3 is the floor, but the description adds real framing on top: it explains that league and price controls distinguish explicit zero from omission and that platform/quality/extinction/search are strictly optional. That reinforces the riskiest parameter semantics rather than restating the schema verbatim.

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?

Names a specific verb and resource ('List native FC27 manager items') and states what the response contains ('source pages, identities and market observations'). It does not name the sibling tools it might be confused with (futgg_fc27_manager, futgg_fc27_manager_facets), only alludes to 'manager facet' selectors, so an agent must infer the boundary itself.

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?

Gives implicit direction that facet queryValue selectors and native pagination are available and optional, but never states when to choose this list tool over the singular manager lookup or the facets tool. The 'zero vs omission' warning is the closest thing to decision guidance, and it applies only to two fields.

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

All Crawlora MCP tools Inspect

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

Need Help?