Skip to main content
Glama

land_stake_dec_overall

Retrieve the overall DEC staking figure for a Splinterlands player's land account, returned exactly as the upstream API reports it. Use it to get the single staked DEC total without regional breakdown.

Instructions

Get the single DEC staking figure the upstream returns for one account, as GET /land/stake/dec/overall returns it. A successful response is {status, data}, where data is a bare JSON number rather than an object or an array; this server returns it exactly as received and does not convert, round, scale or combine it, and a change in that wire type would be reported as a malformed response rather than converted silently. What the number counts, and over what scope, is not stated by the response and is not claimed here. This route does not enforce its declared-required player parameter: a call that omits it was measured to answer HTTP 200 with the number zero, the same zero observed for an unscoped call; whether that equals a real account with nothing staked was not tested, so this tool refuses a call with no player rather than return a plausible zero that describes nobody. A name that matches no account was measured to answer with the same kind of figure as a real account, so an answer from this tool establishes neither that an account exists nor that it does not. A zero returned for a named account is a successful answer and is not reported as no result. The per-region tool lists this account's staking rows separately; this server does not add those rows up, does not compare their total with this figure, and does not derive either from the other.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.0.0

TDQS

A4.7/5.0
Behavior5/5

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

With no annotations, the description carries full behavioral burden and does so thoroughly. It discloses the response wire type (bare JSON number), that it does not convert/round/scale/combine, that a missing player returns HTTP 200 with zero but the tool refuses that call, that a nonexistent account returns a figure but does not confirm existence, and that zero is a valid successful answer. This is exceptionally transparent.

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 long but every sentence contributes essential behavioral or scoping information. It is structured logically: what it does, response format, parameter edge cases, existence semantics, and relationship to sibling. It could be slightly tightened, but no sentence is filler.

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 there is no output schema, the description explains the response format in detail. It covers all edge cases (missing player, nonexistent account, zero result) and clarifies that it does not derive or compare with other data. Nothing an agent needs to correctly call and interpret this tool is missing.

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?

The schema has a single 'player' parameter with zero description coverage. The description compensates by referring to 'one account', 'a call that omits it', and 'a name that matches no account', making it clear that 'player' is the account identifier. It also explains the parameter's optionality and the tool's refusal behavior, adding significant meaning beyond the schema.

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: 'Get the single DEC staking figure the upstream returns for one account'. It clearly identifies what is returned and even specifies the exact endpoint (GET /land/stake/dec/overall). The description also differentiates from the per-region tool by explicitly stating it does not combine rows, so it distinguishes itself from land_stake_dec_region and land_stake_dec_staked.

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?

Provides context on when not to use this tool by explaining that the per-region tool lists rows separately and that this tool does not sum them. It also clarifies edge cases like missing player and nonexistent accounts, which informs usage. However, it does not explicitly say 'use this when you need the overall figure' or name a direct alternative, though the implication is clear.

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