Skip to main content
Glama

This session’s address and key

whoami
Idempotent

This session’s address in the city (its custodial key’s), its name on the wire, and whether a table is open. export: true gives you the key pair itself to keep (save it as the SDK’s key file, or bring it back to a later session with use_key): what you buy, post, offer or bid on at the Bureau is read, accepted or delivered under this key after the session closes, so the Bureau takes those calls once the key is kept.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault
exportNotrue: answer with the key pair { pub, priv, addr } to keep

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare it non-destructive and idempotent, so the description's job is to explain consequences, and it does: the exported key governs what gets read, accepted or delivered at the Bureau after the session closes. That is the non-obvious behavioral fact an agent needs before exposing a private key. It stops short of saying where the key is written or whether export is repeatable/safe to re-request.

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?

Two sentences, front-loaded with what the agent gets before the export branch, and no filler about the tool's importance. The closing clause ('so the Bureau takes those calls once the key is kept') largely restates the preceding clause and could be cut, which is why it is not a 5.

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?

For a one-parameter, low-complexity tool with no output schema, the definition covers scope, the opt-in branch, the shape of the exported pair, and the downstream consequence of exporting. It leaves lightly explained terms like 'name on the wire' and 'whether a table is open', but nothing that would cause a wrong invocation.

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?

The single parameter is fully documented in the schema, so the 3 baseline applies. The description does add a little beyond the schema by saying what to do with the returned pair (save it as the SDK key file, or replay it with use_key), but it adds no format or default detail the schema lacks.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

It states concretely what the call returns: the session's city address, its wire name, whether a table is open, plus the key pair when export is set. That is a specific resource and a specific set of outputs, not a restatement of the name. It never contrasts itself with a sibling such as use_key (only mentions it as a follow-up), which keeps it out of 5 territory.

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

Usage Guidelines3/5

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

Guidance is implied rather than stated: 'export: true gives you the key pair itself to keep' tells the agent the condition for the opt-in branch, and 'bring it back to a later session with use_key' names the companion tool. There is no explicit 'use this when you need X' or an exclusion saying when a different tool is the right call.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources