Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

futgg_fc27_objective_group

Read FC27 objective group details from a slug to preserve task rules, completion requirements and source rewards. Distinguishes public completion counts from user progress.

Instructions

Read FC27 objective group detail. Reads a source group slug and preserves task rules, completion requirements, source rewards and optional values. objectivesCompletionCount is a public completion requirement, not user progress. No automatic previous-edition fallback, biography/account data or locally built squad/reward totals.

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
slugYesNative objective group slug from listing

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

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 full load and does substantial work: it lists what is preserved (task rules, completion requirements, source rewards, optional values), disambiguates objectivesCompletionCount as a requirement rather than user progress, and rules out previous-edition fallback, biography/account data and locally built totals. Auth, rate limits and failure modes are not covered, which keeps it below 5.

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?

It is front-loaded with the purpose and packs field semantics and exclusions into a few dense sentences with no filler. The negative-scope list is somewhat telegraphic and could read more naturally, but every clause carries information.

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 single-parameter read with no output schema and no annotations, the description sufficiently explains what data the call returns and what it deliberately omits. The absence of return-shape detail is acceptable since there is no output schema, though it leaves some ambiguity about the response structure.

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?

Only one parameter exists and the schema already documents it at 100% coverage ("Native objective group slug from listing"). The description adds the origin hint "source group slug" but no format, casing, or discovery guidance beyond the schema, so baseline 3 applies.

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?

The description gives a specific verb+resource ("Read FC27 objective group detail") and clarifies the input is a source group slug, which implicitly distinguishes it from the by_ea and by_objective variants. It stops short of naming those siblings explicitly, so the differentiation is inferred rather than stated.

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 only implied: an agent gathers that this is the slug-based lookup, and the "No automatic previous-edition fallback" line hints at a when-not condition. There is no explicit statement of when to prefer this over futgg_fc27_objective_group_by_ea or _by_objective.

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

Deploy Server

Other Tools