Skip to main content
Glama

Whoami

whoami
Read-only

Retrieves the authenticated Orbits user's ID, email, name, role, and API URL to confirm identity and connection context.

Instructions

Usuario autenticado en Orbits (id, email, nombre, rol) y URL de la API.

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

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's added burden is low. It contributes the fact that the result is scoped to the caller's own session rather than an arbitrary user, but says nothing about auth prerequisites or 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?

A single compact sentence with no filler, front-loading the core fact (which user) before the field list. It is slightly dense — the field enumeration and the API URL are compressed into one clause — but nothing is wasted.

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 an output schema present, return values need not be described, and a zero-parameter read-only tool needs little more than a statement of scope. The definition supplies that scope (current authenticated user) and is complete enough to call correctly, missing only explicit tie-breaking against sibling user-lookup tools.

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 no parameter semantics to explain and the baseline is 4. The description correctly spends no words on inputs.

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?

Names a specific resource — the authenticated user in Orbits — and enumerates the identity fields returned (id, email, nombre, rol) plus the API URL. The word 'autenticado' implicitly separates it from id-based lookups like get_user or find_users, though it never states that distinction explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: an agent can infer this is for discovering its own identity/session context, but there is no explicit when-to-use statement and no named alternative (e.g. get_user) for fetching another user's profile. Minimum viable, with a clear gap around disambiguation.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.