Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

futgg_fc27_season_pass

Read FC27 Season Pass reward metadata to retrieve campaign identity, dates, premium currency details, and separate free/premium reward tiers.

Instructions

Read FC27 Season Pass reward metadata. Returns current native campaign identity, dates, nullable premium currency metadata and every reward-tier row. Free and premium rows can share a level number and remain separate in source order. isPremium describes a reward tier, not user entitlement. No purchase, account access, reward aggregation, biography or media fetch.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.17.20

TDQS

A3.9/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 burden and does well: 'Read' establishes read-only behavior, and it discloses notable data quirks an agent would otherwise get wrong (free and premium rows can share a level number and stay separate in source order; isPremium marks a tier, not entitlement). It stops short of saying whether results are cached, paginated, or how large the tier list typically is.

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?

Five short sentences, front-loaded with purpose and payload, then edge-case notes, then scope exclusions. No filler, and the telegraphic final sentence still communicates scope efficiently.

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?

There is no output schema, so the description must sketch the return shape; it does so at a useful level (identity, dates, nullable premium currency, tier rows). A bit more field-level detail on the reward-tier row structure would make it fully self-sufficient for a no-parameter read tool.

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?

The tool takes zero parameters, which is the baseline-4 case. The description adds clarity about the returned fields (isPremium, premium currency metadata), but those are outputs rather than inputs, so there is no parameter meaning to expand.

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 opens with a specific verb and resource ('Read FC27 Season Pass reward metadata') and then enumerates what comes back: campaign identity, dates, premium currency metadata, and every reward-tier row. That is enough for an agent to tell it apart from catalog/player/objective siblings, though it never names a sibling to route away from.

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 by the narrow scope and the negative scoping sentence ('No purchase, account access, reward aggregation, biography or media fetch'), which rules out adjacent intents. However, there is no explicit statement of when to call this versus a related FC27 tool, and no prerequisites or rate-limit context.

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