Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

Resolve an ADA Handle

resolve_handle
Read-onlyIdempotent

Resolve an ADA Handle ($name, or sub@root for subhandles) to the address that currently holds it, with its stake address and whether a script (for example a marketplace listing) holds it. Use it before sending-related answers or to turn a $handle into an address for other tools.

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": {
      "handle": "<handle>"
    },
    "name": "resolve_handle"
  }
}

Input Schema

NameRequiredDescriptionDefault
handleYesHandle with or without the leading $, e.g. "$snek".

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 declare readOnly, idempotent, non-destructive, open-world behavior, so the safety bar is met. The description adds real value beyond that by warning that resolution may land on a script address (e.g. a marketplace listing), which materially affects how an agent should interpret and act on the result.

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?

Two sentences, no filler. The resolution outcome and its three returned facts come first, with the usage guidance trailing, so the defining information is front-loaded.

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?

There is no output schema, so the description must describe the return, and it does: address, stake address, and script-holder flag. Combined with the 100%-covered input schema and read-only annotations, an agent has everything needed to call and interpret this tool.

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 single parameter is documented with an example, so the baseline is 3. The description adds meaningful semantics the schema pattern does not convey: the $ prefix is optional and the @ form denotes a subhandle, which clarifies how the pattern should be read.

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 (resolve) and resource (ADA Handle) and enumerates the returned facts: holding address, stake address, and whether a script such as a marketplace listing controls it. The handle syntax ($name, sub@root) makes it distinguishable from listing tools like get_wallet_handles or generic address lookup via get_address.

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?

Explicitly says to use it "before sending-related answers" and to "turn a $handle into an address for other tools," which gives a clear workflow trigger. It does not state when-not to use it or name a competing sibling (e.g. get_address / get_wallet_handles), so it falls short of a full routing statement.

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