Crawlora MCP

Official

Overview Schema Source Related Servers Discussions Admin

futgg_fc27_objectives

Browse FC27 objective groups by category and page, including expiry and unreleased-preview metadata, to retrieve native JSON results for tracking available and upcoming objectives.

Instructions

Browse FC27 objective groups. Preserves native category, preview, expiry and pagination arguments/results. Current source quirk: omitted hide_expired hides expired groups, while explicit true or false both include them. The API forwards the native flag without locally correcting it. Full mode returns data only; paginated mode has currentPage,next,totalPages and no invented totalCount. 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	Native one-based page, default1
`page_size`	No	Native size; nonpositive resolves default30; ignored in full mode
`hide_expired`	No	Native flag; omission and explicit presence differ as described
`category_slug`	No	Native group category
`no_pagination`	No	Return native complete data-only envelope
`include_unreleased`	No	Include source-published taskless preview metadata

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.17.20Nov 12, 2026

TDQS

A3.8/5.0

Behavior4/5

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

With no annotations provided, the description carries the full disclosure burden and does substantial work: it surfaces the hide_expired omission quirk, notes the API forwards the native flag without correction, and states exactly which pagination fields appear (currentPage, next, totalPages) with no invented totalCount. It doesn't cover permissions or rate limits, but for a read-only browse endpoint the important behavioral surprises are disclosed.

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 action, then the quirks, then the negative scope. Dense but every sentence carries information; the opener about 'preserves native category, preview, expiry and pagination arguments/results' is the vaguest part and borders on filler.

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 six-parameter read-only browse tool with no output schema, the definition covers the mode split, the response envelope in paginated mode, the expired-flag quirk, and what the tool deliberately does not aggregate. Enough to call correctly; only the relationship to the single-group siblings is left unaddressed.

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; the description goes beyond it by explaining the counterintuitive hide_expired omission-versus-explicit behavior and by clarifying that full mode returns data only while paginated mode returns envelope fields. The phrasing 'preview, expiry and pagination arguments/results' is loosely worded but ties parameters to modes usefully.

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 objective groups') and names the domain clearly. It does not distinguish itself from nearby siblings such as futgg_fc27_objective_group, futgg_fc27_objective_group_by_ea or futgg_fc27_objective_categories, so the agent must still guess which of the group-level tools to call.

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?

Usage is implied rather than stated: the description distinguishes full mode from paginated mode and lists negative scope ('No local expiry windows, squad building, account progress or reward aggregation'), which helps rule out use cases. However, there is no explicit 'use this when' guidance or named alternative for fetching a single group versus browsing a list.

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

Deploy Server