Skip to main content
Glama

Who am I

whoami
Read-onlyIdempotent

Returns the organization this MCP connection is scoped to and its granted scopes. Takes no arguments. Use it to verify the connection and the service token.

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.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds the return content (organization plus granted scopes), which is meaningful because there is no output schema to carry it. It says nothing about failure modes or token expiry, which keeps it off a 5.

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 is returned and followed by input shape and usage. Nothing is padded and no sentence could be dropped without losing 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 no-argument read tool with no output schema, the description covers what is returned and when to call it, which is essentially the full burden. Only the absence of any disambiguation from get_my_setup keeps it below complete.

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?

Zero parameters, so the baseline is 4, and the schema plus "Takes no arguments" make it unmistakable that nothing needs to be supplied. There is no additional semantic work a parameter section could do here.

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?

"Returns the organization this MCP connection is scoped to and its granted scopes" gives a specific verb (returns) and specific resources (organization, granted scopes), so an agent knows exactly what it gets back. It stops short of naming a sibling it is not, which matters here because get_my_setup sits in the same conceptual space.

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?

"Use it to verify the connection and the service token" states a concrete situation for calling it, which is more than most identity tools offer. There is no explicit exclusion or routing away from get_my_setup, so the agent must infer the boundary between the two.

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