Skip to main content
Glama

Idhall Get User

idhall_get_user

Retrieve an IDhall user's record by user ID, optionally limiting the returned fields with props.

Instructions

Récupère la fiche d'un utilisateur IDhall par son ID.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "user_id": "<user_id>"
    },
    "name": "idhall_get_user"
  }
}

Input Schema

NameRequiredDescriptionDefault
propsNo
user_idYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the whole burden. 'Récupère' does convey a non-mutating read of a single record, which is useful behavioral signal, but nothing is said about failure behavior (missing/invalid user) or any access restrictions. The presence of an output schema relieves it of explaining return values, which keeps this at a 3 rather than lower.

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, front-loaded sentence with no filler or repetition. It is efficient, though its brevity comes at the cost of the missing parameter and usage detail noted elsewhere.

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 two-parameter tool with zero schema description coverage, no annotations, and an unexplained 'props' argument, the description is too thin. It also leaves the relationship to idhall_list_users unresolved; only the existence of an output schema reduces what the description must cover.

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% for two parameters. The description only clarifies user_id ('par son ID'), which the parameter name already implied, and says nothing about the 'props' parameter, whose purpose (likely selecting which fields to return) is entirely undocumented in both schema and description.

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 states a specific verb ('Récupère') plus a specific resource ('la fiche d'un utilisateur IDhall') and the lookup key ('par son ID'), so an agent can tell it fetches a single user record rather than a list. It does not name or differentiate itself from the sibling idhall_list_users, which is the main thing keeping it from a 5.

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 implied only: 'by their ID' signals a direct-lookup scenario versus a search or list, but the description never states when to prefer this over idhall_list_users or what to do when the ID is unknown. There are no preconditions or exclusions stated.

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