Skip to main content
Glama

Resolve the caller's accounts

whoami

Works with an OAuth2 bearer token (user principal). Plain API keys are account-scoped and get 403 here; then use the account id from Account settings in the Docuflex app and pass it as account_id or x-docuflex-account.

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
api_keyNoDocuflex API key (dfx_live_...). Optional if sent as the x-docuflex-api-key header.
account_idNoDocuflex account id. Optional if sent as x-docuflex-account or if the key belongs to exactly one account.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does disclose a real constraint: write/auth scope differences between OAuth2 user tokens and plain API keys, including a 403 failure mode. It omits what the call actually returns (no output schema exists), retry behaviour, and whether the 403 is recoverable without a re-issue, so the disclosure is partial.

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 dense sentence pair with no wasted words, but it is front-loaded with authentication rather than with what the tool returns, and the semicolon-clause 'then use the account id...' reads as a recovery instruction rather than a purpose statement.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a zero-required-parameter identity tool with no output schema, the description should at least indicate what 'whoami' yields (user principal, account list, account ids). Instead it is entirely about the credential path, leaving an agent unable to predict the response it will get back.

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?

Schema coverage is 100%, so the schema already documents api_key, account_id, the 200/64 length caps, the header alternatives, and the single-account fallback. The description only adds where to obtain the account id ('Account settings in the Docuflex app'), which is modest incremental value over the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description never states what the tool does; it only describes authentication mechanics. The name 'whoami' and title 'Resolve the caller's accounts' carry the purpose, so an agent can infer identity resolution, but the description itself adds no verb+resource statement and does not distinguish this from siblings like docuflex_overview or request_access.

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?

It gives a usable condition: OAuth2 bearer (user principal) is required, and plain API keys are account-scoped and get 403 here. That implicitly tells the agent when this call will fail and how to recover via account_id, but there is no explicit 'use this when' framing or mention of any alternative tool for account-scoped operations.

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