Skip to main content
Glama

Check granted scopes

whoami
Read-onlyIdempotent

Which Gambit account this connection acts for, and your API key's granted scopes and what each unlocks. Call this before attempting writes, or when a tool returns a 401/403 scope error, instead of retrying. Everything YOUR tools write (Gambits, facts, views, saved Gambits, signals) lands on this account: when the user may have more than one account, tell them which one before a write. account: display_name, email (masked, d***@domain) and main_wallet (shortened), null when the key lacks api:read or the lookup failed; key: id, key_prefix, label, kind (api_key or connector), scopes and created_at.

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds substantive context beyond them: fields are masked or shortened, account is null when the key lacks api:read or the lookup failed, and writes land on this account so the user should be told which account when multiple exist. That is return-shape, failure-mode, and side-effect disclosure in one place.

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 core identity/scope answer and the call condition, then the field listing. Dense but every clause carries information; the inline enumeration of fields is the only part that slightly crowds the prose.

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?

No output schema exists, and the description compensates by enumerating the returned account and key fields, their masking, and their null conditions. Nothing an agent needs in order to call this correctly or interpret the result is missing.

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?

The tool takes zero parameters, so there is nothing to disambiguate; baseline 4 applies. The description instead spends its words on the response shape, which is the right allocation.

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 resource pair – the Gambit account the connection acts for plus the API key's granted scopes and what each unlocks. No sibling tool covers identity/scope introspection, so an agent can distinguish it immediately from its listed siblings.

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?

Gives explicit trigger conditions ('before attempting writes', 'when a tool returns a 401/403 scope error') and an explicit anti-pattern ('instead of retrying'). This is the when/when-not/alternative structure at full strength.

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