Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

futgg_fc27_objective_group

Read-only

Read one current-edition FC27 objective group by its source slug and preserve task rules, completion requirements, source rewards and optional values. objectivesCompletionCount is a public completion requirement, not user progress. Get the slug from futgg_fc27_objectives; there is no automatic previous-edition fallback, and biography, account data and locally built squad/reward totals are excluded.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "slug": "<slug>"
    },
    "name": "futgg_fc27_objective_group"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesRequired native objective group slug from the listing. The numeric prefix is the group EA id, not a database id and not a child objective EA id.

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.3/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds real behavioral context beyond that: no previous-edition fallback, and explicit exclusions of biography, account data and locally built squad/reward totals. The clarification that objectivesCompletionCount is a public completion requirement rather than user progress preempts a very plausible misreading of the payload.

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?

Every sentence carries distinct information: purpose, field semantics, slug provenance, edition behavior, and exclusions. It is dense and the middle clauses run together, but nothing is redundant and the purpose is front-loaded.

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 return values need not be described; the description instead covers the non-obvious parts — edition fallback behavior, slug provenance, and what is deliberately excluded. Only the choice among the sibling lookup variants remains 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% and the slug property already explains that the numeric prefix is the group EA id, so the baseline is 3. The description adds provenance the schema does not — where to obtain the slug (futgg_fc27_objectives) — which meaningfully improves correct invocation.

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?

The description opens with a specific verb+resource+scope: 'Read one current-edition FC27 objective group by its source slug.' The 'current-edition' and 'by its source slug' qualifiers plus the instruction to source the slug from futgg_fc27_objectives let an agent distinguish this from the by_ea and by_objective siblings without opening schemas.

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?

It explicitly routes the agent to futgg_fc27_objectives for the slug and states a hard exclusion ('there is no automatic previous-edition fallback'), which is genuine when/when-not guidance. It stops short of naming when to prefer futgg_fc27_objective_group_by_ea or _by_objective instead, so selection among the lookup variants is left partly to inference.

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