Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

futgg_fc27_sbc_sets

Browse FC27 squad building challenges using native category, search, expiry filters, and pagination to retrieve challenge metadata, rewards, and prices as JSON.

Instructions

Browse FC27 squad building challenges. Reads native category/search/expiry filters and pagination. Both expiry flags true preserve the source's expired-only precedence. no_pagination=true returns the native data-only envelope and ignores pagination controls; no metadata is synthesized. Native page_size<=0 resolves its default. Preserves rewards, challenge metadata, published prices and null/false/zero values; excludes biography, account/render flags and unreviewed editorial data.

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

Input Schema

Name	Required	Description
`page`	No	One-based native page; default1; ignored in full-list mode
`search`	No	Native SBC search text, up to1024bytes
`page_size`	No	Native integer page size; nonpositive uses source default24; ignored in full-list mode
`expired_only`	No	Native expired-only selector; explicit false preserved
`category_slug`	No	Native category from discovery
`expiring_soon`	No	Native expiring-soon selector; expired_only=true takes source precedence
`no_pagination`	No	Native full-list mode; source returns data without page fields

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

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 disclosure burden and does substantial work: it declares no_pagination returns a native data-only envelope with no synthesized metadata, that expired_only takes source precedence over expiring_soon, and that null/false/zero values and prices are preserved. It omits read-only/safety framing, error behavior, and response shape (page fields present only when 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?

Purpose is front-loaded in the first sentence and every subsequent clause conveys a distinct behavioral fact. The phrasing is dense and semicolon-chained with compressed negation lists ('excludes biography, account/render flags and unreviewed editorial data'), which costs readability but not information density.

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 seven-parameter read tool with no annotations and no output schema, the definition covers filtering precedence, pagination modes, defaulting behavior, and what fields are preserved or excluded. The main gap is that neither output schema nor description specifies the returned list item structure, requiring the agent to infer it from the 'preserves' clause.

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%, so each of the seven parameters is already documented, and the description largely restates that (page_size nonpositive default, expired_only precedence). It adds modest value by clarifying that pagination controls are ignored in full-list mode, but most parameter meaning is duplicative of the schema.

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: 'Browse FC27 squad building challenges', with filtering and pagination scoping. It does not explicitly distinguish itself from siblings like futgg_fc27_sbc_categories or futgg_fc27_sbc_set, so an agent must infer that 'Browse' + plural means a list versus a single-set lookup.

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?

The description explains the semantics of individual controls (expiry flag precedence, no_pagination full-list mode, ignored pagination in full-list mode), which implies when to use them. It never states when to prefer this tool over sibling SBC endpoints or when pagination versus full-list mode is appropriate for the agent's task.

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

Deploy Server