Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

land_projects_history

Retrieve a deed's land project history by plot_id or deed_uid, with optional limit and offset for pagination. Get clear records to track project changes.

Instructions

List the land project records the upstream returns for one deed uid. The recorded history probes were a bare request, offset=1, limit=2, and limit=2&offset=2: limit=2 narrowed from the start, while offset=1 and offset=2 did not reach later rows in those requests. This answer is additionally bounded to at most 100 rows and 256 KB by this server; if it is cut for that reason, the response reports that local bound. The project-count tool returns the count the upstream reports for this deed; whether that count covers exactly the records this tool would return has not been verified. 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
limitNo
offsetNo
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

A4.8/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. It reveals the probe-observed offset/limit behavior, server-side bounds of 100 rows and 256 KB with a reported local cut, the possibility of an extra verified deed GET before the target GET, and the content of resolved results. This is unusually transparent and adds significant context beyond a simple capability statement.

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?

Every sentence adds distinct value and the purpose is front-loaded in the first sentence. However, the dense seven-sentence paragraph mixes pagination probes, local bounds, count-tool caveats, input rules, and resolution details, making it less scannable than a structured format with bullets or clearer separation of concerns.

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 absence of annotations, output schema, and parameter descriptions, this description covers input constraints, server-side response bounds, pagination quirks, relationship to the count tool, and resolution behavior. Almost nothing an agent needs to call this tool correctly is missing.

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%, so the description must compensate. It explains that plot_id can be numeric or a display label, that deed_uid accepts the original spelling, and that exactly one of them must be supplied. Limit and offset semantics are indirectly conveyed through the probe descriptions, though a more precise definition of offset would have been clearer. Overall, it adds meaningful meaning to every parameter.

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 a specific verb ('List'), a specific resource ('land project records'), and a specific scope ('for one deed uid'). It also distinguishes itself from the count tool by noting the project-count tool returns the count rather than the records.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It explicitly tells the caller to supply exactly one plot_id (numeric or display label) or deed_uid, and notes that the original UID spelling is accepted. It also names the project-count tool as the count alternative and flags the uncertainty about whether that count matches this tool's records, plus the resolution behavior with a two-request cap.

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