Skip to main content
Glama

Who am I

whoami
Idempotent

Identify the authenticated account and its linked wallets, and list the local signing keys this process holds, including the Solana settlement address to use on Solana legs.

Instructions

The account you are authenticated as (linked wallet addresses), plus localSigners.addresses — what THIS process holds keys for (any key that could not be read is reported separately under localSigners.unusable, and solanaLink says whether the Solana wallet held here is proven to the account — an order whose give leg is Solana needs that). Use localSigners.addresses.solana as your settlement address on a Solana leg: the server builds that transaction for whoever the leg names, so naming a key you do not hold makes the leg unsignable.

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

No arguments

Output Schema

NameRequiredDescriptionDefault
idNoAccount id
errorNoSet instead when the call failed
solanaLinkNo
localSignersNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.11.1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "error": {
      +      "additionalProperties": {},
      +      "description": "Set instead when the call failed",
      +      "properties": {
      +        "code": {
      +          "type": "string"
      +        },
      +        "is_retryable": {
      +          "type": "boolean"
      +        },
      +        "message": {
      +          "type": "string"
      +        },
      +        "recovery_hint": {
      +          "type": "string"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "id": {
      +      "description": "Account id",
      +      "type": "string"
      +    },
      +    "localSigners": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "addresses": {
      +          "additionalProperties": {
      +            "type": "string"
      +          },
      +          "description": "Keys held here, per chain",
      +          "propertyNames": {
      +            "type": "string"
      +          },
      +          "type": "object"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "solanaLink": {
      +      "type": "string"
      +    }
      +  },
      +  "type": "object"
      +}
  2. Addedv0.10.0

TDQS

A3.7/5.0
Behavior4/5

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

Goes well beyond the annotations by disclosing that unreadable keys appear under `localSigners.unusable`, that `solanaLink` reports whether the held Solana wallet is proven to the account, and the failure consequence: naming a key you don't hold makes the leg unsignable. That failure-mode disclosure is exactly the context annotations can't carry. The odd `readOnlyHint: false` on a pure identity query is not contradicted by any claim in the text.

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-loads the identity statement, then the key-holding distinction, then the operational rule and its failure mode. Dense but each clause carries information; the nesting of backticked paths inside a single long paragraph makes it slightly harder to scan than it needs to be.

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 no-parameter, read-style identity tool with an output schema, this is close to complete: it explains the two halves of the response, the unusable-key bucket, the proof flag, and the practical consequence of misusing an address. Missing only explicit guidance on when in a workflow to call it relative to siblings.

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?

Zero input parameters, so the baseline is 4, but the description's parameter-like content is about output fields rather than inputs. It adds real meaning to response fields (`localSigners.unusable`, `solanaLink`), though the output schema already exists and covers them, so the added value is moderate rather than decisive.

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?

States a specific resource: the authenticated account with linked wallet addresses, plus `localSigners.addresses` — what the local process holds keys for. The account-vs-key distinction is precise and an agent can tell it apart from `set_settlement_address`. It doesn't explicitly name siblings, which keeps it from a 5.

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?

Gives one concrete usage rule — use `localSigners.addresses.solana` as the settlement address on a Solana leg — but that is guidance about interpreting output, not when to call this tool versus `set_settlement_address` or other siblings. When-to-call is only implied (check identity/keys before signing).

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