Skip to main content
Glama

Idhall Whoami

idhall_whoami

Identifies the user tied to the current JWT and retrieves their IDhall profile, so AI clients can confirm identity and load the correct user record.

Instructions

Identifie l'utilisateur associé au jeton JWT courant et récupère sa fiche IDhall.

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": "idhall_whoami"
  }
}

Input Schema

NameRequiredDescriptionDefault
propsNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations, the description still conveys the key behavioral facts: the operation is token-scoped (JWT required) and read-only in nature ('récupère'). It does not say how an expired or missing token surfaces (error vs. empty result), which matters for an auth-dependent tool with zero annotation coverage.

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?

One sentence with no filler, and the token-scoping constraint is front-loaded. It is well sized for the tool, though it leaves no room for the parameter hint it should have included.

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?

An output schema exists, so return values need not be described, and the auth requirement is stated. The remaining gap is the unexplained 'props' argument and the absence of routing guidance against idhall_get_user.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% and the single parameter is named 'props' (nullable array of strings, default null), which is opaque on its face. The description never mentions this parameter at all, so it fails to compensate for the coverage gap or explain what properties are being requested.

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?

The description names a specific verb and resource: it identifies the user bound to the current JWT and fetches that user's IDhall profile. The phrase 'jeton JWT courant' implicitly separates it from idhall_get_user and idhall_list_users, which operate on explicit user identifiers, though no sibling is named outright.

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 the tool for 'who am I / current session user'. There is no explicit statement of when to prefer it over idhall_get_user, nor any note about what happens when no valid token is present.

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