Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Address or stake key on the explorer

get_address
Read-onlyIdempotent

Explorer view of a payment address (addr1…) or stake address (stake1…): type, whether it is a script, ADA balance, tokens held (decimal-adjusted, valued in ADA), the stake key, delegation and rewards (ADA) for stake addresses, and first/last activity. For portfolio value in USD use get_wallet instead.

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": {
      "address": "<address>"
    },
    "name": "get_address"
  }
}

Input Schema

NameRequiredDescriptionDefault
addressYesaddr1… or stake1… (resolve a $handle with `resolve_handle` first).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, openWorld), so the description's job is to add data-shape context — which it does, noting token amounts are decimal-adjusted and ADA-valued and that delegation/rewards apply only to stake addresses. It stops short of covering failure modes (invalid address, unregistered stake key, not-found), which would have pushed it higher.

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?

Front-loaded with the resource and address types, then a dense but purposeful field list, then the alternative-tool pointer. The middle clause is a long enumeration packed into one sentence, slightly harder to scan than a bulleted list, but no sentence is wasted.

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?

With no output schema, the description must describe return values — and it does so field by field with units (ADA) and adjustment notes (decimal-adjusted), which is the critical gap for a single-parameter read tool. Only error/empty-case behavior is left unstated.

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?

Schema coverage is 100% and the pattern/min-length rules are in the schema, so the baseline is 3. The description earns one extra point by explaining the behavioral split between the two accepted forms (addr1… vs stake1…), which the schema does not convey.

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 (explorer view of a payment or stake address) and enumerates exactly what is returned: type, script flag, ADA balance, tokens, stake key, delegation/rewards, first/last activity. It also names the concrete alternative (`get_wallet`) for USD portfolio value, so the tool is distinguishable from siblings without opening any schema.

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

Usage Guidelines5/5

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

Explicitly routes the agent: use this for an on-chain address/stake-key explorer view, use `get_wallet` instead when the goal is portfolio value in USD. The schema further points at `resolve_handle` for `$handle` inputs, so the hand-off chain is clear.

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