Crawlora MCP

futgg_fc27_objectives

Read-only

Browse native FC27 objective groups and preserve source category, preview, expiry and pagination arguments and results. Source quirk: omitting hide_expired hides expired groups while an explicit true or false both include them, and the API forwards the flag without correcting it. no_pagination=true returns the data-only envelope; paginated results carry currentPage, next and totalPages but no invented totalCount. category_slug comes from futgg_fc27_objective_categories. No local expiry windows, squad building, account progress or reward aggregation.

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

Input Schema

Name	Required	Description
`page`	No	Optional one-based native page, default 1; ignored in full mode.
`page_size`	No	Optional native page size. A nonpositive value resolves the source default of 30; ignored in full mode.
`hide_expired`	No	Optional native flag. Source quirk: omitting it hides expired groups, while an explicit true or false both include them; the flag is forwarded without local correction.
`category_slug`	No	Optional native group category from futgg_fc27_objective_categories: coming-soon, foundations, seasonal, campaigns, live-events, milestones, mastery or fc-pro. The separate Season Pass campaign row is not a category and the UI-only Expiring Soon filter is not a server selector.
`no_pagination`	No	Optional native full mode: the source returns a data-only envelope.
`include_unreleased`	No	Optional native flag that includes source-published taskless preview metadata.

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 11, 2026

TDQS

A4.1/5.0

Behavior5/5

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

Read-only annotations are already present, yet the description still adds real value: it discloses the source quirk that omitting hide_expired hides expired groups while an explicit true or false both include them, and that the flag is forwarded uncorrected. It also describes envelope shape differences between modes (currentPage/next/totalPages, no invented totalCount), which an agent cannot get 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?

Purpose is front-loaded in the first clause, followed by quirk and mode details in a compact paragraph. It loses a little efficiency by restating the hide_expired quirk that the schema already documents verbatim, and the trailing 'No local …' list is terse but useful for scoping.

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?

With an output schema present the description need not explain return values, yet it still characterizes both envelopes, and it covers the source quirk and category provenance comprehensively. The only notable gap is routing versus the singular objective_group siblings and the by_* lookup variants, which are not addressed.

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 description coverage is 100%, so the baseline is 3; every parameter already carries its own description including the hide_expired quirk and the category enumeration. The description adds only marginal extra meaning (where category_slug originates, what the data-only envelope implies), so it does not clearly exceed 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 native FC27 objective groups') plus what is preserved (category, preview, expiry, pagination). It implicitly points at futgg_fc27_objective_categories as the slug source and explicitly rules out out-of-scope concerns, but it never contrasts itself with the similarly named futgg_fc27_objective_group / objective_group_by_* siblings.

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?

Gives clear operating context: paginated mode vs no_pagination=true full mode, and that category_slug must be obtained from futgg_fc27_objective_categories. Exclusions are stated ('No local expiry windows, squad building, account progress or reward aggregation'), though no sibling is named as the alternative for those capabilities.

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.