Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

futgg_fc27_sbc_set_by_ea

Read-only

Read one native FC27 squad-building-challenge set by its EA set id and return the same public set/challenge/reward metadata as futgg_fc27_sbc_set. Take id from a listing row's eaId: it is not the set database id and not an EA challenge id. No account, biography or solver execution.

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

Input Schema

NameRequiredDescriptionDefault
idYesRequired positive EA set id from a listing row's eaId. This is not the set database id and not an EA challenge 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?

With readOnlyHint and openWorldHint already declared, the description still adds useful context: 'public' metadata scope and 'No account, biography or solver execution', telling the agent no auth or solve run is triggered. It stops short of describing size, caching, or error behavior for a missing eaId, which would push it to a 5.

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 tight sentences, front-loaded with what the tool does, then the identifier constraint, then the negative scope. Every clause carries routing or scoping information; nothing is padding.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/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 shape need not be explained, and the annotations carry the read-only/open-world profile. For a one-parameter lookup, the remaining burden is identifier disambiguation and side-effect disclosure, both of which are covered.

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 coverage is 100% and the single parameter's schema description already says 'not the set database id and not an EA challenge id', so the description's near-identical wording in the body is reinforcement rather than new meaning. The addition of 'positive' and 'from a listing row's eaId' is consistent with but not beyond the schema.

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?

States a specific verb and resource ('Read one native FC27 squad-building-challenge set by its EA set id') plus the exact return content ('same public set/challenge/reward metadata as futgg_fc27_sbc_set'). It also distinguishes itself from the sibling it most resembles, futgg_fc27_sbc_set_by_challenge, by naming which identifier keys the lookup.

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 concrete sourcing guidance: take the id 'from a listing row's eaId' and explicitly rules out the set database id and the EA challenge id, which implicitly routes the agent to futgg_fc27_sbc_set / futgg_fc27_sbc_set_by_challenge for those keys. It never states the positive alternative by name ('if you have the database id, use futgg_fc27_sbc_set'), so the routing is inferred rather than spelled out.

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