Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

futgg_fc27_sbc_sets

Read-only

Browse native FC27 squad-building challenges with the source's own category, search, expiry and pagination selectors, returning native set rows with rewards, challenge metadata, published prices and preserved null/false/zero values. Both expired_only and expiring_soon true keep the source's expired-only precedence; no_pagination=true returns the native data-only envelope and ignores paging controls, while an omitted page resolves page 1 and a nonpositive page_size resolves the source default 24. page 0 or a page past the end is the source's 404. Biography, account/render flags and unreviewed editorial data are excluded.

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

NameRequiredDescriptionDefault
pageNoOptional one-based native page, default 1; ignored when no_pagination is true.
searchNoOptional native SBC search text, up to 1024 bytes.
page_sizeNoOptional native page size. A nonpositive value uses the source default of 24 and is not locally clamped; ignored when no_pagination is true.
expired_onlyNoOptional native expired-only selector; an explicit false is preserved.
category_slugNoOptional native category slug from futgg_fc27_sbc_categories: players, upgrades, challenges or foundations. The UI's virtual Expired/Expiring Soon tabs are listing flags, not category slugs.
expiring_soonNoOptional native expiring-soon selector; expired_only=true takes the source's expired-only precedence when both are set.
no_paginationNoOptional native full-list mode: the source returns the data array without pagination fields, and paging controls are ignored rather than synthesized.

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

A4.6/5.0
Behavior5/5

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

Beyond the readOnly/openWorld annotations, it discloses precedence rules (expired_only wins over expiring_soon), the no_pagination envelope behavior, default page size 24, page-0/out-of-range 404, and which fields are excluded. This is rich behavioral context an agent could not infer 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?

Front-loaded with the core purpose, then edge-case rules. It is dense and long, but nearly every clause carries a distinct behavioral fact, so little is wasted.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With an output schema present, return values need not be explained, and the description covers the remaining edge cases (pagination defaults, 404, precedence, exclusions) thoroughly for a 7-param listing tool.

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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema does not: expired_only precedence over expiring_soon, nonpositive page_size resolving to 24, and page 0 mapping to a 404. That is genuine added value beyond the per-field schema text.

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?

States a specific verb (browse) and resource (native FC27 squad-building challenges / SBC sets), and the scope (category, search, expiry, pagination selectors) clearly separates it from the singular futgg_fc27_sbc_set detail sibling.

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?

Explains the selector semantics and points to futgg_fc27_sbc_categories for valid category slugs, giving clear context for when to use this listing tool. It stops short of explicitly contrasting with the singular set-detail siblings, so it is not a full when/when-not statement.

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