Skip to main content
Glama

Who am I

whoami
Read-onlyIdempotent

The workspace (its name, currency, time zone and week start), the member and role of this token, the access of the token (read, or read and write), and which money the role sees (money.amounts, money.costs). Call it first: dates are in the time zone of the workspace, and a money field that the role does not see is left out of every result.

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
moneyYesWhich money the role shows: a field of money that the role hides is never in a result
tokenYes
memberYes
workspaceYes

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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior beyond that: time-zone semantics for all dates and the fact that a money field the role cannot see is silently dropped from results rather than nulled or errored. It stops short of noting per-token variance or caching, but the result-shaping disclosure is the important part.

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?

One dense enumerative sentence plus a two-clause directive — nothing is wasted, and the call-first instruction and the two interpretive caveats are packed into very little text. It opens with a subject-less noun phrase ('The workspace...') rather than a verb-first statement of purpose, which is a minor front-loading weakness, but the density is otherwise exemplary.

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?

An output schema exists, so the description is not obligated to enumerate return values, and for a zero-parameter read tool the main risks are misinterpretation of dates and absent money fields — both addressed. The one remaining gap is that it does not say what happens if the token is invalid or the workspace is ambiguous, though the single-token, closed-world model makes that low risk.

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 no parameters, so the baseline of 4 applies. The description correctly spends no space on inputs and instead redirects that space to output semantics.

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 names a specific resource set — workspace settings (name, currency, time zone, week start), the member and role behind the token, the token's read/read-write access, and which money fields the role can see. That is far more than a restatement of 'whoami' and lets an agent predict the exact contents of the response, distinguishing it from every resource-getting sibling.

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?

It gives an explicit imperative: 'Call it first,' and then supplies the reason that makes the guidance actionable — dates come back in the workspace time zone and money fields can be omitted. This tells the agent both when to call it (before interpreting results) and why skipping it would cause misinterpretation. No exclusion cases are needed because no sibling overlaps in purpose.

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