Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

fortnite_ecosystem_metrics

Read-only

Returns platform-wide Fortnite peak client and in-match user count data series. Use this for ecosystem trends; provide an interval and optional inMatchPeakCCU or inClientPeakCCU filters.

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": {
      "interval": "<interval>"
    },
    "name": "fortnite_ecosystem_metrics"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoOptional exclusive ISO-8601 end time.
fromNoOptional inclusive ISO-8601 start time, within the seven-day history window.
metricsNoOptional repeatable exact ecosystem metric filter.
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.5/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 that the output is a data series and that results are platform-wide, but says nothing about the seven-day history ceiling, pagination, or sample density beyond what the schema states.

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 sentences, front-loaded with what is returned before usage guidance, with no filler. Minor imprecision: the metric filter values are phrased as if they were parameters ('optional inMatchPeakCCU or inClientPeakCCU filters') rather than the allowed values of the metrics array.

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, full schema coverage, and read-only annotations, the definition supplies enough for correct invocation. The main remaining gap is routing guidance against the singular fortnite_ecosystem_metric and island-level metric siblings.

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 interval, from, to, and metrics in detail. The description only echoes that interval is required and names the two metric filter values, adding no format or interaction detail beyond the schema — the baseline 3 applies.

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 ('Returns') and a precisely scoped resource ('platform-wide Fortnite peak client and in-match user count data series'). The 'platform-wide' qualifier implicitly separates it from island-level siblings such as fortnite_island_metrics, but no sibling is named explicitly.

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?

The sentence 'Use this for ecosystem trends' gives a positive when-to-use context, but there is no exclusion guidance and no named alternative for per-island or single-metric queries, leaving the agent to infer the boundary from sibling names alone.

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