Crawlora MCP

futgg_fc27_manager_facets

Read-only

List the current FC27 manager-specific nation and league choices and return source facet counts, native queryValue mappings and supported platform/quality/extinction values. Use these with futgg_fc27_managers; the unresolved null league maps to queryValue 0. 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_manager_facets"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

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

A4.3/5.0

Behavior4/5

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

Goes beyond the readOnly/openWorld annotations by disclosing the shape of the response (facet counts and native queryValue mappings) and a non-obvious edge case: the unresolved null league maps to queryValue 0. It omits data freshness or rate-limit caveats, keeping it just short of a 5.

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 compact sentences, front-loaded with what is returned and then the companion-tool guidance plus the null-league caveat. 'Takes no input' mildly restates the empty schema but usefully closes the question for an agent.

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, so the description need not detail return payloads, yet it still characterizes them; combined with the zero-param schema and annotations, an agent has what it needs. Only novelty/churn of facet values is left unstated.

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?

Takes no input, and the description explicitly confirms that with 'Takes no input', matching the empty schema. Nothing further is owed for a zero-parameter tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Uses a specific verb ('List') with a precise resource ('FC27 manager-specific nation and league choices') and enumerates the returned artifacts (facet counts, native queryValue mappings, platform/quality/extinction values). This clearly separates it from futgg_fc27_managers and futgg_fc27_manager_leagues.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly tells the agent to use these values with futgg_fc27_managers, which is the key routing guidance for a facet helper. It does not state when to avoid it, but for a zero-parameter lookup tool the context is clear.

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?