Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Cardano Wrapped 2026 card

get_wrapped_card
Read-onlyIdempotent

Cardano Wrapped 2026: one wallet's year on Cardano (trading, NFTs, staking, governance, an archetype and ranks) with a link to the shareable card. Opens 1 December 2026; before that the tool answers with the launch date and no card. A wallet can opt out, and then there is no card. The first request for a wallet computes the card, which can take a few seconds.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "id": "<id>"
    },
    "name": "get_wrapped_card"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe wallet: a $handle, a stake1… address or an addr1… address that has a stake part.
refreshNoRecompute the card instead of reading the stored one (honoured at most about once an hour per wallet).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the read-only, idempotent, non-destructive, open-world profile. The description adds useful behavioral details beyond annotations: launch-date gating, opt-out suppression, and first-request computation latency ('can take a few seconds'). It could mention rate limits or permission requirements more explicitly, but the added context is substantial.

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?

Four tight sentences, front-loaded with the purpose, then gating, opt-out, and latency. Every sentence earns its place by adding distinct usage or behavioral context.

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?

Without an output schema, the description still explains the return values sufficiently: a card with a link, a launch-date notice, or no card if opted out. Annotations cover safety, schema covers parameters, and the description covers timing and computation behavior—complete for an agent to call it 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?

Schema description coverage is 100%, so the schema already documents the id and refresh parameters fully. The description adds no additional parameter-level semantics beyond what is already in the schema, aside from the general context that a wallet may opt out. Baseline 3 is appropriate when the schema does the heavy lifting.

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 states a specific verb+resource: 'Cardano Wrapped 2026: one wallet's year on Cardano' and details the exact contents (trading, NFTs, staking, governance, archetype, ranks, shareable card link). It is clearly distinct from sibling wallet tools like get_wallet or get_wallet_pnl because it describes an annual recap, not raw wallet data.

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 temporal context: 'Opens 1 December 2026; before that the tool answers with the launch date and no card.' It also explains opt-out behavior. However, it does not explicitly name or contrast with sibling tools, though no direct alternative exists for this specific recap card.

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

All Realtap 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