Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

land_liquidity_pool_by_id

Retrieve a single liquidity pool's details by its ID, returning resource quantities, shares, and prices while clearly distinguishing unknown IDs from malformed ones.

Instructions

Get one liquidity-pool object by id, as GET /land/liquidity/pools/{id} returns it. A real id returned a single object with a narrower field set than the list route, omitting the one-day and thirty-day volume fields. An unknown well-formed id returned HTTP 200 with data:null, while a malformed id returned HTTP 400; these are distinguishable upstream outcomes. The object fields retain the mixed wire types observed on the list route: resource_quantity, dec_quantity and total_shares are JSON strings, while prices are JSON numbers. This server returns the upstream response unchanged and does not turn data:null into an error or manufacture a pool object.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYes

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 provided, the description carries full disclosure burden. It thoroughly discloses return field omissions, type inconsistencies (strings vs numbers), error handling (data:null vs 400), and the server's pass-through behavior. No contradictions; every behavioral trait is explained.

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?

Every sentence earns its place: the purpose is front-loaded, behavioral nuances are grouped logically, and there is minimal redundancy. The description is detailed but efficient, fitting several critical facts into a compact paragraph.

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 tool with no annotations and no output schema, this description is remarkably complete. It covers the return shape, field types, error semantics, and upstream behavior, leaving little for an agent to infer. It also explains the difference from the list route, which is essential for correct selection.

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?

The single parameter 'id' is covered by the schema with type and minimum, and the description adds context about how different id validity states affect the response, effectively giving semantic meaning beyond the raw schema. Since schema coverage is 0%, this compensation is valuable.

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 precise verb ('Get') and resource ('liquidity-pool object by id'), and explicitly distinguishes it from the list route by noting it returns a single object with a narrower field set. The route pattern is given, making the tool's purpose unambiguous and differentiated from siblings like land_liquidity_pools.

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 clear behavioral expectations for different id scenarios (real, unknown well-formed, malformed) and explains the resulting HTTP outcomes, which guides usage. However, it does not explicitly name alternative tools (e.g., land_liquidity_pool_by_symbol) or state when to prefer this over them, though the 'by id' nature is implicit.

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