Skip to main content
Glama

Crawlora MCP

fortnite_island_metric

Read-only

Returns one metric data series for a selected Fortnite island. Use an island code from fortnite_islands, then provide the interval and metric path value; retention is daily only.

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>",
      "interval": "<interval>",
      "metric": "<metric>"
    },
    "name": "fortnite_island_metric"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional exclusive ISO-8601 end time.
codeYesRequired island code or first-party display name.
fromNoOptional inclusive ISO-8601 start time, within the source's seven-day history window.
metricYesRequired source metric path variant.
intervalYesRequired upstream bucket size: day, hour, or minute (ten-minute samples).

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.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds one genuinely new behavioral fact — "retention is daily only" — which constrains which interval/metric combinations are valid, but it says nothing about rate limits, empty-result behavior, or how the seven-day history window interacts with retention metrics.

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?

Two compact clauses, front-loaded with the return behavior and followed by the workflow and constraint. Nothing is padded, though the semicolon-joined second sentence packs three distinct ideas that would read more clearly separated.

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 explanation is unnecessary. Given that, the description covers purpose, the upstream dependency for obtaining the island code, and the one non-obvious availability constraint (daily-only retention), which is enough for an agent to call this correctly.

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 every parameter is already documented, including the ISO-8601 from/to bounds and the day/hour/minute interval values. The description restates the interval and metric requirements without adding syntax, defaults, or valid metric-path examples beyond what the schema provides, so it lands at the baseline.

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 and resource: "Returns one metric data series for a selected Fortnite island." The singular "one metric" implicitly distinguishes it from the plural sibling fortnite_island_metrics, but it never names or contrasts that sibling 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?

It gives a useful prerequisite chain: get the island code from fortnite_islands, then supply interval and metric. However, it never says when to pick this tool over fortnite_island_metrics or fortnite_island_rankings, and it doesn't state what to do if an invalid metric path is supplied.

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