Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

land_plot_snapshot

Read-onlyIdempotent

Read one plot's deed, active project, stake details and stake assets from four public endpoints. Supply a numeric plot_id or padded region-tract-plot label.

Instructions

Read one plot's deed, active project, stake details and stake assets from four public endpoints. Supply a numeric plot_id or padded region-tract-plot label. Optional include selects sections from deed, active_project, stake_details and stake_assets; the default is all four. The deed is always read because it verifies the plot identity and supplies the deed UID, but it is returned only when included. include=["deed","stake_details"] makes two GETs. The follow-up reads run in parallel after the deed read. Each call reads afresh and returns a whole result only when the deed identity is verified and every selected follow-up read succeeds; a failed read returns no partial result, although the other parallel reads may already have been sent. Null active project is a valid no-project result. No account defaults, cache or inferred plot data.

Input Schema

NameRequiredDescriptionDefault
includeNo
plot_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.7
    • addedInput schema / properties / include
      Added value: +{
+  "items": {
+    "enum": [
+      "deed",
+      "active_project",
+      "stake_details",
+      "stake_assets"
+    ],
+    "type": "string"
+  },
+  "maxItems": 4,
+  "minItems": 1,
+  "type": "array"
+}
  2. Addedv1.0.5

TDQS

A4.4/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: four GETs, deed always read for identity verification, follow-up reads parallelized after the deed read, whole-or-nothing result semantics with no partial result on failure, null active project as a valid outcome, and explicit no-cache/no-account-defaults behavior. This is exactly the kind of context the readOnly/idempotent hints cannot convey.

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?

Front-loads the purpose, then layers addressing, include semantics, and failure behavior. Every sentence carries information, though the parallel-read and partial-result caveats are dense and require close reading.

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?

For a multi-endpoint read tool with no output schema and no parameter docs in the schema, the description covers invocation, identity verification, failure semantics and null-project handling well. It stops short of describing the shape/fields of the returned sections, but the resource set is named clearly enough for selection.

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?

With 0% schema description coverage, the description carries the full burden and does: it defines the plot_id formats (numeric vs padded region-tract-plot label) and explains include's selectable sections, the all-four default, and the counterintuitive rule that deed is always read but returned only when included.

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 ('Read') and a precise composite resource: a single plot's deed, active project, stake details and stake assets from four endpoints. This clearly distinguishes it from single-domain siblings such as land_deed_by_plot, land_stake_details and land_projects_active.

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?

It explains how to address the plot (numeric plot_id or padded region-tract-plot label) and how include works, but never states when to prefer this aggregate over the individual siblings (e.g., land_deed_by_plot, land_stake_assets) or when-not to use it. Usage is implied rather than routed.

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