Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

fortnite_islands

Read-only

Lists public Fortnite islands with Epic's native before/after cursors and page size. Tags are free-form; use fortnite_genres for the closed genre list. Creator account codes are omitted.

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": "fortnite_islands"
  }
}

Input Schema

NameRequiredDescriptionDefault
sizeNoOptional upstream page size from 1 through 1000; default 100.
afterNoOptional upstream pagination cursor. Use next_cursor or links.next from the prior response.
beforeNoOptional upstream pagination cursor for results before this position.

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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered. The description adds non-structured behavioral context beyond them: results are public-only islands, pagination uses Epic's native cursors rather than an internal scheme, and creator account codes are omitted from results. It does not mention rate limits or auth, keeping it below a 5.

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?

Three short sentences with zero filler: the core operation and pagination model come first, the sibling routing rule second, and the field caveat last. Every sentence carries distinct information.

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, return values need not be explained, and all three optional parameters are schema-documented. The description adds the key data caveat (account codes omitted) and the tag-vs-genre distinction. It could say more about ordering or result caps, but nothing needed to call it correctly is missing.

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 coverage is 100%, so size, after and before are already fully documented in the input schema. The description only adds the framing that these are Epic's native pass-through cursors and a page-size concept, which is marginal value over the schema wording 'upstream pagination cursor'. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Lists public Fortnite islands') plus the scope qualifier 'public', and explicitly names the sibling tool fortnite_genres as the one that covers the closed genre list. An agent can distinguish this enumeration tool from the singular fortnite_island and genre siblings without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives one explicit routing rule: use fortnite_genres for the closed genre list, implying this tool is for free-form tag filtering or plain enumeration. It lacks an explicit statement of when not to use this tool (e.g. vs fortnite_island_rankings or fortnite_island for single-record lookups), so it falls short of full when/when-not coverage.

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