Skip to main content
Glama

land_resources_leaderboards

Get Splinterlands land resource leaderboard entries for a specific resource symbol. Filter by player, region, or territory to see ranked rows with amounts and production rates.

Instructions

List the resource-leaderboard rows the upstream returns, as GET /land/resources/leaderboards returns them. A successful response is {status, data}, where data is an array of rows carrying rank, player, amount, amount2, resource_per_hour, guild, title_pre, data and id. The numeric fields are JSON numbers, and this server returns them unchanged; it does not convert, round, total or compare them, and a change in their wire type would be reported as a malformed response rather than converted silently. The nested data field is a JSON-encoded string, not an object; this server returns it exactly as received and does not parse it, and a change in that wire type would be reported as malformed rather than converted. The upstream matches resource case-sensitively against its exact symbol. This tool uppercases resource before making the request, but it does not enforce an enum because the observed symbols are not a declared exhaustive set. Omitting resource returned HTTP 400. Omitting region with no territory produced no HTTP response in two measurements and timed out; territory was observed to work standalone without region, so this tool refuses only when both region and territory are absent. That refusal is this server's safety choice based on the observed hang, not an upstream validation rule. Supplying player returned that player's row in addition to the normal top rows. Paging probes supplied offset=0, offset=5, page=2 and from=5; each returned parsed data equal to the limit=5 baseline. limit=50 returned 50 rows whose first five matched that baseline in the same order, and no ceiling was found at the tested limits 5 and 50. No value tried for offset, page or from produced a later slice. This tool reports the rows the upstream returned and nothing else.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNo
playerNo
regionNo
resourceYes
territoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4.5/5.0
Behavior5/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure, and it does so exceptionally well. It reveals that numeric fields are returned unchanged without conversion, the nested data field is a JSON string not parsed, resource is uppercased, and the tool refuses when both region and territory are absent due to an observed hang. It also documents paging probe results and malformed-response handling. This is far beyond minimal disclosure.

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?

The description is a single dense paragraph, not concise in length, but every sentence contributes unique information about behavior, edge cases, or response format. It is front-loaded with the primary purpose and then expands into necessary details. While not structured with bullets or headings, the content is well-organized and each sentence earns its place.

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?

Given the lack of an output schema and annotations, the description is exceptionally complete. It details the response structure, parameter semantics, paging behavior, and even states 'This tool reports the rows the upstream returned and nothing else.' An agent has everything needed to invoke this tool correctly and anticipate its responses.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It thoroughly explains each parameter's behavior: resource is required and uppercased, player adds that player's row, region/territory interaction, and limit/offset/page/from behavior. It even notes that no paging parameter produced a later slice. This adds substantial meaning beyond the bare schema properties.

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?

The description clearly states the tool's function: it lists resource-leaderboard rows as returned by the upstream GET endpoint. It names the specific resource (leaderboards) and distinguishes it from sibling tools by the endpoint path. The verb 'List' plus the resource name and explicit reference to the upstream API make the purpose unambiguous.

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 description provides extensive behavioral notes about parameter usage (e.g., omitting resource returns 400, region/territory interaction, paging behavior) but does not explicitly state when to choose this tool over alternatives. It lacks a clear 'use this when...' statement or mention of sibling leaderboard tools like player_leaderboard. The edge-case guidance is useful but does not address tool selection.

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

Deploy Server

Other Tools