Skip to main content
Glama
Sign In

Realtap

by io.github.CSteenkamp
OverviewDiscussionsAdmin

One Masumi agent service

get_masumi_agent
Read-onlyIdempotent

Everything indexed about one entry of the Masumi registry: full description, price, API endpoint, capability, author, tags, when and by which transaction it was registered, who holds the registry token, and its latest payments from the escrow contract with their status (locked, result submitted, paid, refunded). Get the identifier from list_masumi_agents.

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_masumi_agent"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesAgent identifier: the registry policy id followed by the asset name, in hex (the `id` of `list_masumi_agents`).

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 safety profile: read-only, idempotent, non-destructive, and open-world. The description adds useful behavioral context by enumerating the returned data, including escrow payment statuses such as locked, result submitted, paid, and refunded.

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?

The description is front-loaded with the core purpose and then lists exactly what is returned. The second sentence cleanly handles the identifier dependency, with no wasted wording.

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, but the description compensates by enumerating the key returned fields and payment statuses. Combined with the annotations and the fully documented single parameter, it gives the agent enough information to call the tool 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 `id` parameter is already well documented as the hex registry policy id plus asset name. The description adds provenance by saying to get it from `list_masumi_agents`, but it does not add format or validation detail beyond the schema.

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 and resource: retrieve everything indexed about one Masumi registry entry. It distinguishes itself from `list_masumi_agents` by emphasizing 'one entry' and explicitly points to that sibling for obtaining the identifier.

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?

It clearly tells the agent that the required identifier comes from `list_masumi_agents`, giving concrete usage context. It does not explicitly state when not to use this tool, but the one-entry scope makes its role 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