Skip to main content
Glama

Who am I

whoami
Read-onlyIdempotent

Returns the Nextset user id this connection is signed in as, and whether that account is allowed in Nextset. It answers which account the assistant is connected to, and why other tools may say the account isn't allowed.

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

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds value beyond them by disclosing the two pieces of information returned and the diagnostic significance of the allow flag, though it does not state the exact response shape (field names, error behavior when unauthenticated).

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?

Two compact sentences, front-loaded with what is returned and followed by the diagnostic purpose. Minor overlap between 'which account the assistant is connected to' and the first sentence's 'signed in as', but the second idea earns its place.

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-parameter read tool with no output schema, the description covers identity, scope, and return semantics adequately. A brief note on what the response looks like when the account is not allowed would close the remaining 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 and the baseline applies. Mentioning that the result is scoped to 'this connection' usefully clarifies there is no account argument to pass.

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 and return content: the Nextset user id the connection is signed in as, plus an allow/deny flag for that account. It also frames the tool's role in the catalog ('why other tools may say the account isn't allowed'), which no sibling covers given names like get_athlete_context or get_logs.

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?

It gives a clear trigger — use it to learn which account the assistant is connected to, or to diagnose an 'account isn't allowed' error raised by other tools. It stops short of explicit when-not-to-use guidance or naming an alternative, but there is no evident sibling that overlaps, so the omission is minor.

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