Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

land_resources_production_region_harvestable

Retrieve harvestable resource production rows for a Splinterlands account and land region, showing claimable amounts and required resources per token.

Instructions

List the harvestable resource rows the upstream returns for one account and one land region, as GET /land/resources/production/region/harvestable returns them. A successful response is {status, data}, where data is an array of rows carrying amount_claimable, grain_required_for_food, wood_required, stone_required, iron_required and token_symbol. All 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 upstream returned HTTP 400 with Invalid parameters passed when either player or region_uid was missing, and this tool requires both before making the request. A fake player or region_uid returned data:[], a successful empty answer. This tool reports the rows the upstream returned and nothing else.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerYes
region_uidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  2. First observedv0.0.0

TDQS

A4.3/5.0
Behavior5/5

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

With no annotations, the description carries the full disclosure burden and does so thoroughly: it gives the response shape {status, data}, the exact row fields, numeric wire-type behavior, the upstream 400 on missing parameters, and the successful empty data:[] response for fake IDs. It also explicitly states the tool reports only the upstream rows and nothing else.

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 front-loaded with purpose and response shape, and every paragraph contributes useful operational detail about edge cases and numeric handling. It is slightly dense and the final sentence restates a point already made, but there is no significant filler.

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 no output schema and no annotations, the description provides a solid output contract including field names, response wrapper, numeric behavior, and common failure modes. It could still add explicit account-name or region-uid format details and clearer sibling differentiation, but an agent has enough information to call the tool and interpret its response.

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 0%, and the description does not define the value semantics of player or region_uid beyond what the names imply. It usefully notes that both are required, that missing values trigger the upstream 400, and that fake values yield an empty data array, but it lacks format or domain guidance for these two string parameters.

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 opens with 'List the harvestable resource rows', a specific verb and resource, and scopes it to one account and one land region. It also names the upstream endpoint, making the tool's function and read-only nature unmistakable and distinguishable from the many sibling land_resources_* tools.

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?

The description clearly states when to use the tool: to retrieve harvestable production rows for a single player/region pair. It also specifies the prerequisite that both player and region_uid are required before making the request, though it does not explicitly name alternatives or when-not-to-use conditions.

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