Skip to main content
Glama
Sign In

SCVD General Store

by store.scvd
OverviewDiscussionsAdmin

Read a Binder

read_binder
Read-onlyIdempotent

Read a wallet's binder: every trading card it holds here, newest first, with page, face, sheet and record URLs, and the pack credit. Free, no account. A listing, not a proof; the signed records are. Completes when the result carries cards and count.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "wallet": "0x2222222222222222222222222222222222222222"
    },
    "name": "read_binder"
  }
}

Input Schema

NameRequiredDescriptionDefault
walletYesA 0x address (forty hex characters) or a base58 Solana address.

Output Schema

NameRequiredDescriptionDefault
cardsYesNewest first.
countYesCards listed.
walletYesThe wallet, as keyed.
truncatedNoTrue when the binder holds more than one page lists.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the safety profile is covered; the description adds real value beyond them by specifying no auth or cost ('Free, no account'), result ordering ('newest first'), the fields returned, and a completion condition ('Completes when the result carries cards and count'). It does not mention rate limits or pagination, which keeps it out of the top band.

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 core action is front-loaded and no sentence is filler, but the telegraphic fragments ('A listing, not a proof; the signed records are') read as clipped and cost a little clarity for their brevity.

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?

With a single required parameter, a full output schema, and rich annotations, the description covers what is left: cost, auth, ordering, returned fields, and termination. Nothing an agent needs to call this correctly is missing.

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?

There is a single wallet parameter and schema description coverage is 100% — the schema already documents the 0x/base58 address formats. The description adds nothing about the parameter, so the high-coverage baseline of 3 applies.

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 specific verb and resource (read a wallet's binder) and enumerates the payload ('every trading card it holds here, newest first, with page, face, sheet and record URLs, and the pack credit'). It also draws a sharp boundary against proof-oriented siblings with 'A listing, not a proof; the signed records are,' so the agent can separate it from verify_artifact or buy_signed_record.

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?

'Free, no account' establishes preconditions that gate invocation, and 'A listing, not a proof; the signed records are' implicitly routes proof-checking to another tool. It stops short of naming that sibling explicitly or stating a when-not-to-use condition, so it is clear context rather than full routing guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SCVD General Store toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources