Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

rentals_by_bid

Retrieve delegation rental records for a specific bid transaction ID, returning 1 to 100 entries per request.

Instructions

Read legacy SPSP delegation rental records for an explicit bid transaction ID and limit of 1 to 100. A populated bid response matched the corresponding player rental record. Preserve numeric wire strings. Paging and sort effectiveness are not established; one bounded response, no automatic continuation. These are token delegation rentals, not worker-card rentals. Makes one logical GET request Does not auto-fetch continuation pages. Required inputs reflect tool policy as well as measured upstream requirements. Other declared filters are forwarded as supplied; their effectiveness is not implied by the schema. The data list are locally limited to 100 rows and 256 KiB, with truncation reported in text and metadata. Oversized records are refused without partial fields.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
bidYes
sortNo
limitYes
orderNo
offsetNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.0.2
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. First observedv0.0.0

TDQS

A4.1/5.0
Behavior5/5

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

With no annotations, the description carries the behavioral burden and meets it: it discloses one logical GET, no auto-continuation, unreliable paging/sort, 100-row/256 KiB local cap, truncation reporting, refusal of oversized records, and preservation of numeric wire strings.

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

Conciseness2/5

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

The description repeats the same behavioral ideas: 'no automatic continuation', 'one bounded response', 'Makes one logical GET request', and 'Does not auto-fetch continuation pages' are near-duplicates. It is front-loaded but not tightly written.

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 parameter-rich endpoint with no annotations or output schema, the description covers invocation inputs, limits, truncation behavior, and pagination reality. It does not specify the response object shape, but that is partially offset by the explicit mention that truncation is surfaced in text and metadata.

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?

Schema coverage is 0%, and the description compensates for bid ('explicit bid transaction ID') and limit (1-100), plus a blanket warning that other declared filters are forwarded with no implied effectiveness. However, sort, order, and offset receive no individual semantic explanation.

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 specifies a clear verb and resource: 'Read legacy SPSP delegation rental records' for 'an explicit bid transaction ID'. It also explicitly disambiguates from sibling endpoints with 'These are token delegation rentals, not worker-card rentals,' which lets an agent distinguish this from rental_bids, rentals_by_player, and similar tools.

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 tool is scoped to a bid transaction ID, and the description includes a when-not signal ('not worker-card rentals'). It does not name an alternative endpoint to prefer in other cases, but the bidding context and exclusion are clear enough.

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