Skip to main content
Glama

fortnite_island_metrics

Read-only

Returns native aggregate metrics for an island. Intervals are day, hour and minute (ten-minute samples); history is seven days. Metrics are averageMinutesPerPlayer, peakCCU, favorites, minutesPlayed, recommendations, plays, uniquePlayers and retention. Retention is daily only; average minutes is omitted for minute buckets. Null values mean data is unavailable for that interval.

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

Input Schema

NameRequiredDescriptionDefault
toNoOptional exclusive ISO-8601 end time.
codeYesRequired island code or first-party display name.
fromNoOptional inclusive ISO-8601 start time. Upstream history is limited to seven days.
metricsNoOptional repeatable exact metric filter; supported values are all listed in the enum.
intervalNoOptional upstream bucket size. Omit for the source's default daily range.

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 and openWorldHint, so the description focuses on data behavior and adds real value: a seven-day history limit, interval-specific metric omissions, and the meaning of null values. It stops short of covering pagination, rate limits, or the shape of the aggregation, but the availability semantics are well disclosed.

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?

Four tight sentences, front-loaded with the purpose and then the constraints, with no filler. The metric enumeration partially duplicates the schema's metric list, which is the only mild redundancy.

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?

An output schema exists, so return values need not be explained, and the description covers the interval model, the seven-day history window, per-interval metric availability, and null semantics. The remaining gap is not distinguishing this tool from its singular/rankings siblings when an agent has several near-identical options.

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 100%, so the baseline is 3, and the description earns above that by explaining that interval supports day, hour, and minute (ten-minute samples) — detail the schema's 'Optional upstream bucket size' does not give — and by noting retention is daily-only. It does not clarify 'from'/'to' exclusivity beyond what the schema already says.

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?

States a specific verb and resource ('Returns native aggregate metrics for an island') and enumerates exactly which metrics come back, so the agent knows what it gets. It does not differentiate itself from near-identical siblings such as fortnite_island_metric or fortnite_island, which is the only thing keeping it from 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?

Usage is implied by the description of what data is available at each interval, and the constraints ('retention is daily only', 'average minutes omitted for minute buckets') effectively guide which interval to choose. However, there is no explicit statement of when to use this tool versus the singular metric or rankings siblings.

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.