Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

futgg_fc27_objective_group_by_ea

Retrieve FC27 objective group metadata by EA group ID to get public parent group details, excluding account state and cross-edition fallback.

Instructions

Read FC27 objective group by EA group ID. Uses group eaId, not its internal database id or a child objective EA id. Returns the same public parent group metadata as the slug resource, without account state or cross-edition fallback.

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": {
      "id": "<id>"
    },
    "name": "futgg_fc27_objective_group_by_ea"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPositive EA group ID from listing eaId

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the burden and does disclose meaningful traits: read-only access, absence of account state, and no cross-edition fallback, plus that output mirrors the slug resource's public metadata. It omits error/not-found behavior and response shape, which matters given there is no output schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the action and the key constraint, with zero filler. Every clause either states scope or prevents a specific misuse.

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 tool with no output schema, it covers what the returned data is and what it is not (no account state, no edition fallback). It could go one step further in describing the returned parent-group fields now that no output schema exists to do so.

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 already 100% ("Positive EA group ID from listing eaId"), so the baseline is 3, and the description earns more by ruling out two plausible but incorrect id interpretations. That disambiguation is the single most error-prone part of calling this tool and is spelled out.

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 states a specific verb and resource ("Read FC27 objective group") and narrows it by the exact key type (EA group ID), which separates it from the sibling lookup keyed by objective. It alludes to a slug-based sibling resource without naming it, so differentiation is clear but not fully explicit.

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 gives usable selection guidance by specifying which identifier to supply and explicitly excluding two wrong inputs (internal database id, child objective EA id). It stops short of naming an alternative tool for those other id types, so the agent must infer routing rather than being told it.

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