Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

land_resources_liquidity_swaps

Retrieve liquidity-swap rows for a given player, returning raw transaction data across all pool IDs. Use it to obtain a player's swap history without interpretation or totals.

Instructions

List the liquidity-swap rows the upstream returns for one player, as GET /land/resources/liquidity/swaps/{player} returns them. A real account returned 682 rows spanning all six observed pool ids. The rows carry numeric ids, quantities and pool quantities, string player/token/transaction fields and timestamp strings; this server returns each row unchanged and does not interpret or total the figures. An unknown player returned HTTP 200 with data:[], a different empty shape from the data:null used by the two pool lookup routes. An empty array therefore establishes neither that the account exists nor that it has no swaps.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
playerYes

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.5/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 burden and does so thoroughly. It discloses passthrough behavior ('returns each row unchanged'), explicitly states it does not interpret or total figures, and documents the surprising unknown-player behavior (HTTP 200 with data:[] rather than data:null). It even provides a concrete example of row count and pool coverage.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is front-loaded with the core purpose and then each subsequent sentence adds a distinct, non-redundant fact: row quantity, field types, passthrough behavior, and the empty-array semantics. No sentence is wasted.

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?

For a single-parameter list endpoint with no output schema, the description covers what the rows contain, how they are returned, and how to interpret the empty-array edge case. It gives enough behavioral context for an agent to call the endpoint and correctly interpret the response without further guidance.

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?

The only parameter, 'player', is mentioned as 'one player' in the description and its behavior for unknown values is explained, but the description does not specify player name format, case sensitivity, or how it relates to other player identifiers in sibling tools. Since schema coverage is 0%, the description only partially compensates for the lack of schema-level parameter documentation.

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?

Description specifies a clear verb ('List'), a precise resource ('liquidity-swap rows ... for one player'), and the exact upstream route pattern. It also differentiates this route from pool lookup routes by noting the different empty response shape.

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 gives clear context: use it when you need the raw liquidity-swap rows for a specific player, and it explicitly warns that the server does not interpret or total figures. It contrasts with pool lookup routes but does not name a specific sibling alternative for when a different tool should be used.

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