Skip to main content
Glama

Pagetool

Who am I

whoami
Read-onlyIdempotent

Reports who the caller currently is: an authenticated account, an anonymous draft holder, or nobody. Never errors on absent credentials. You do not need to call this before building - building needs no identity at all.

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
draft_tokenNoThe draft token returned by draft_create, if you are working on an anonymous draft. Only needed when your client cannot send the x-pagetool-draft-token header.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description still adds real behavioral content beyond them: the 'never errors on absent credentials' guarantee and the three discrete outcome states, which matter given there is no output schema. It does not say what payload shape accompanies each state.

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?

Three short sentences, front-loaded with what the tool returns, followed by the error guarantee and then the anti-pattern warning. No redundant restatement of the name or title, and every sentence carries distinct information.

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 zero-required-parameter read tool with no output schema, the definition covers outcome states, error behavior, and the main misuse risk. The only missing piece is any hint about the shape or fields of the returned identity information, which an agent probing auth state might want.

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?

There is one optional parameter and schema description coverage is 100%, so the schema already explains draft_token and its relationship to the x-pagetool-draft-token header. The description adds nothing about the parameter, which is acceptable at full coverage but is the baseline rather than an improvement.

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 verb and resource ('Reports who the caller currently is') and immediately enumerates the three possible states: authenticated account, anonymous draft holder, or nobody. An agent can tell this apart from identity-adjacent siblings like draft_create or draft_claim without opening a schema.

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?

Gives an explicit exclusion: 'You do not need to call this before building - building needs no identity at all,' which preempts the most likely over-invocation. It stops short of naming a sibling tool or describing a positive trigger scenario beyond 'reporting who the caller is,' so it is clear but not fully two-sided.

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