Skip to main content
Glama

Crawlora MCP

fortnite_island_rankings

Read-only

Returns Epic's hourly rank history for an island using an optional inclusive from and exclusive to range within seven days. With no bounds, the source returns its latest snapshot.

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": {
      "code": "<code>"
    },
    "name": "fortnite_island_rankings"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional exclusive hourly snapshot end time.
codeYesRequired island code or first-party display name.
fromNoOptional inclusive hourly snapshot start time, within the seven-day history window.

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

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely new behavioral context: a hard seven-day history window, inclusive start vs. exclusive end semantics, and the no-bounds fallback to the latest snapshot. It stops short of noting rate limits, pagination, or snapshot cadence.

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?

Two sentences with no filler: the scope and range rules come first, followed by the default behavior. Every clause carries information an agent needs to call the tool correctly.

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?

With an output schema present and full schema coverage, the description need not explain return values, and it correctly focuses on the range semantics and default. The only gap is mild: no guidance on sibling tools or on what the time strings should look like.

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 description coverage is 100%, so the schema already documents code, from, and to. The description restates the same inclusive/exclusive semantics and the seven-day window rather than adding new meaning such as accepted time formats or what a 'first-party display name' resolves to. Baseline 3 is appropriate.

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 uses a specific verb ('Returns') and a specific resource ('Epic's hourly rank history for an island'), so an agent can tell it apart from metric tools like fortnite_island_metric without opening the schema. It does not explicitly name a sibling alternative, which keeps it just short of a 5.

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?

It states the default behavior when no bounds are supplied ('the source returns its latest snapshot'), which implies the caller should provide from/to for historical ranges. However, it never says when to prefer this over fortnite_island or fortnite_island_metric, and no exclusions or prerequisites are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources