Skip to main content
Glama

Who am I

whoami
Read-onlyIdempotent

Start here. The organization this key belongs to, its plan and usage (accounts and posts this month, X posts and X link posts left), whether the key may publish (scope, claimed sandbox and a plan in force; why_not says what is missing, and without publishing only drafts work), the key's caps, and — in a sandbox — the claim state. Use can_publish to decide between drafting and scheduling. app_only lists what only a person can do in the app, and why.

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/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), and the description adds real context beyond them: sandbox claim state, why_not diagnostics, and app_only human-only actions. What's missing is any statement about the shape of the response, but the field-level enumeration largely compensates.

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?

'Start here' is correctly front-loaded and no sentence is filler. The middle sentence is a long, comma-and-em-dash-heavy list that takes effort to parse, and the 'X posts and X link posts left' placeholders read oddly, but density rather than bloat is the flaw.

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?

With no output schema, the description is the sole source of return-value documentation, and it enumerates the key fields an agent needs before acting. Precise response structure and field names are only implied, which leaves a small residual gap.

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 for the description to disambiguate; the baseline of 4 applies. No parameter guidance is needed or expected.

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?

The description effectively defines the tool as an introspection/orientation call, enumerating exactly what it returns (org, plan, usage, publish eligibility, caps, sandbox claim state). 'Start here' plus the return enumeration makes the role clear against siblings like list_workspaces or list_members, though it never explicitly names an alternative.

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?

'Start here' gives an unambiguous first-call directive, and 'Use can_publish to decide between drafting and scheduling' routes the agent's next decision. It stops short of saying when not to call it or naming a competing sibling, so it falls just short of a 5.

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