Skip to main content
Glama
Silverkazimi

splinterlands-mcp

by Silverkazimi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

player_avatar

Resolve a player's legacy profile avatar URL by reading the official endpoint's redirect. Returns avatar_url, image_url, and redirect status without downloading image bytes.

Instructions

Resolve one player's legacy profile image link, which may be a round RUNI portrait rather than card artwork and is not the avatar-builder character. RUNI card and square artwork variants are documented in library/avatar-artwork.md; this tool resolves only the selected profile link. Reads the official avatar endpoint once logically, inspects its HTTP 302 Location without following it, and returns avatar_url, image_url and redirect_status. Only HTTPS Splinterlands-domain image destinations are accepted. No image bytes are downloaded; the current image URL may change. A returned avatar does not prove the account exists. No credentials or game writes.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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 present, the description fully carries behavioral disclosure and does so richly. It details the single logical HTTP read, the 302 Location inspection without following it, the returned fields, HTTPS domain restrictions, no image download, URL volatility, non-proof of account existence, and no credentials/game writes.

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 description is front-loaded with purpose and each sentence adds a useful caveat or behavioral detail. It is longer than strictly necessary for a one-parameter tool, but the extra sentences earn their place given there is no output schema and no annotations.

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 low-complexity tool with one parameter and no output schema, the description covers the main behavioral, security, and side-effect concerns well. It names the three return fields, but does not fully define redirect_status values or error behavior, which is a minor completeness gap.

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 schema only defines name as a string with minLength 1, and schema coverage is 0%. The description implies that the name identifies the player whose legacy profile link is resolved, and even notes that a returned avatar does not prove the account exists, which adds behavioral meaning to the parameter. It does not specify account-name format or case sensitivity, but for a single obvious string parameter this is adequate.

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 opens with a specific verb and resource: "Resolve one player's legacy profile image link." It explicitly distinguishes the tool from RUNI card artwork and the avatar-builder character, so an agent can tell it apart from related player/image tools without opening schemas.

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 for use: it is for legacy profile image links, not avatar-builder characters or card artwork variants, and points to documentation for those variants. It does not explicitly name sibling tools like player_custom_avatar, but the exclusions are clear enough for selection.

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