Skip to main content
Glama

whoami

Read-only

Return the authenticated coach (user id, name, email, role) and trainer id. Use to verify the connection.

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. Changed1 schema field changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds genuine value beyond that by enumerating the returned identity fields and noting the data is scoped to the "authenticated" coach, which tells the agent the call depends on the current session. It does not say what happens when there is no valid session, which keeps it from 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?

Two sentences, front-loaded with the return payload, then the intended use. Zero filler for a zero-argument tool.

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 trivial zero-param diagnostic, the description covers purpose, return fields, and usage; no output schema exists, so listing the payload is appropriately done here. The only gap is unauthenticated/error behavior, a minor omission given the tool's simplicity.

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?

Zero parameters, so the baseline of 4 is adjusted only slightly; there is nothing in the schema to add meaning to. The description correctly implies no inputs are needed, but offers no note about defaults or session-derived context that an agent might wonder about.

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 ("Return") and enumerates the exact resource returned: user id, name, email, role, and trainer id. An agent immediately knows this is an identity/self-lookup tool and cannot confuse it with the domain-mutation siblings listed.

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?

Explicitly says when to use it: "Use to verify the connection." That is a clear selection cue for a diagnostics call. It stops short of stating when not to use it (e.g., that it is not a substitute for a role/permission check), so it is not 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.