Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

land_deed_by_uid

Fetch the public land deed record for a Splinterlands plot by deed UID or plot ID to check owner and listing state.

Instructions

Get the public land-deed record for one deed uid. The player field is the owner at read time; market listing fields describe current listing state, not purchase history. Supply exactly one plot_id (numeric or display label) or deed_uid; the original UID spelling is also accepted. Reference resolution may add one verified deed GET before the target GET, with a hard two-request limit. Populated resolved results include all three plot identities and resolution freshness.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
plot_idNo
deed_uidNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • changedInput schema / properties / plot_id / anyOf
      Previous value: -[
-  {
-    "minimum": 1,
-    "type": "integer"
-  },
-  {
-    "type": "string"
-  }
-]New value: +[
+  {
+    "maximum": 9007199254740991,
+    "minimum": 1,
+    "type": "integer"
+  },
+  {
+    "type": "string"
+  }
+]
  2. First observedv0.0.0

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does reasonably well: it discloses non-obvious semantics (player is owner at read time, market listing fields are current state not history), an internal resolution step, and a hard two-request limit. It omits auth/permission needs, but for a public read tool that is minor.

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?

Four dense but purposeful sentences, front-loaded with the core purpose. Each sentence adds distinct information (record identity, field semantics, operand rule, resolution/result behavior); the resolution sentence is jargon-heavy but earns its place.

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?

No output schema exists, but the description compensates by describing what populated resolved results contain (all three plot identities, resolution freshness) and clarifying field semantics. An agent has enough to call and interpret it, though explicit sibling routing is the remaining gap.

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

Parameters4/5

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

Schema coverage is 0% and required params are listed as 0, so the description must compensate; it does by clarifying that plot_id accepts a numeric id or display label, that deed_uid accepts the original spelling, and that exactly one of the two must be supplied. This adds meaningful constraint beyond the bare schema.

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

Purpose4/5

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

The description states a specific verb and resource ('Get the public land-deed record for one deed uid') and scopes it to a single record. It is clear on its own, though it never names or contrasts with the obvious sibling land_deed_by_plot, instead muddying the boundary by saying plot_id may also be supplied.

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 gives a usable operand rule ('supply exactly one plot_id or deed_uid') and notes an alternative spelling is accepted, which is real guidance. However, it never says when to choose this tool over land_deed_by_plot or land_deeds_owned, so sibling routing is left to inference.

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