Skip to main content
Glama

Idhall List Users

idhall_list_users

List IDhall users with pagination, selectable properties, and filters to find and page through relevant user records.

Instructions

Liste les utilisateurs IDhall avec pagination, projection (props) et filtres (UserFilter).

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_list_users"
  }
}

Input Schema

NameRequiredDescriptionDefault
countNo
propsNo
filterNo
offsetNo
page_sizeNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.8/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full behavioral burden. It mentions pagination, projection, and filtering, but those capabilities are already visible in the schema; it does not state permissions, whether the operation is read-only, rate limits, or how `count` affects the response.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single efficient sentence with the resource and key capabilities front-loaded. There is no redundant or filler wording.

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?

With five parameters, 0% schema description coverage, and no annotations, the definition needs substantially more detail. The output schema covers return values, but the description leaves the `filter` shape, `count` semantics, and basic operational behavior undocumented.

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%, so the description must compensate for all five parameters. It labels `props` as projection and `filter` as `UserFilter`, and implies pagination, but it never explains the opaque `UserFilter` structure or the `count` parameter.

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 ("Liste") and resource ("utilisateurs IDhall") and names supported capabilities: pagination, projection, and filters. It does not explicitly differentiate this list operation from sibling read tools such as idhall_get_user or idhall_whoami, so it falls short of 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 Guidelines2/5

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

The description gives no when-to-use guidance, no exclusions, and no alternatives. An agent must infer that this is the bulk user-listing tool rather than the single-user getter or identity checker.

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