Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

cards_lore

Get the lore text for a Splinterlands card by supplying its card_detail_id. Returns the card's lore object without any derived attributes.

Instructions

Get the lore object returned by GET /cards/lore for one card_detail_id. The measured successful response was a bare object with numeric card_detail_id and string text. Omitting card_detail_id returned HTTP 200 with an empty body and no JSON, so this tool requires card_detail_id before making the request. The measured response carried no BCX, donor or account-attribution field. Successful lore responses are cached for 24 hours; provenance reports the route and the original fetch time. This tool returns the lore object unchanged and does not derive card attributes from its text.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
card_detail_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / card_detail_id / maximum
      Added value: +9007199254740991
    • addedInput schema / properties / card_detail_id / minimum
      Added value: +-9007199254740991
  2. First observedv0.0.0

TDQS

A4/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 the measured response shape, the empty-body failure mode when the parameter is omitted, absence of BCX/donor/attribution fields, 24-hour caching, provenance behavior, and the fact that text is not parsed into card attributes.

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?

The purpose is front-loaded in the first sentence, and later sentences are informative rather than filler. It is somewhat verbose for a one-parameter read endpoint, with the omission behavior stated twice, but each remaining sentence earns its place.

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 simple one-parameter endpoint with no output schema, the description covers request requirements, response shape, caching, provenance, and non-derivation behavior. An agent has everything needed to call and interpret this tool correctly.

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 is card_detail_id, and schema description coverage is 0%. The description adds the "one" cardinality and the omission consequence, but it does not explain what a card_detail_id represents beyond what the schema name and integer type already imply.

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 the specific verb "Get", the resource "lore object", the endpoint GET /cards/lore, and the required input card_detail_id. This clearly differentiates it from sibling cards_* tools like cards_skins or cards_get_details.

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

Usage Guidelines2/5

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

The description explains that card_detail_id is required and must be supplied before making the request, but gives no guidance on when to prefer this tool over alternatives. It does not mention any sibling tools or conditions for choosing this endpoint.

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