Gestion MCP Server

list_usuarios

Retrieve users from the backend with optional filters, pagination, and sorting. Requires ADMIN or MANAGER role.

Instructions

List users from the backend with optional filters, pagination, and sorting. Requires ADMIN or MANAGER role.

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

Input Schema

Name	Required	Description
`rol`	No	Filter by role
`page`	No	Page number (0-based)
`size`	No	Page size
`search`	No	Search term to filter by email
`sortBy`	No	Field to sort by
`direction`	No	Sort direction

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

A3.7/5.0

Behavior3/5

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

The only behavioral disclosure is the role requirement. No annotations are provided, so the description carries the full burden. It does not mention response format, pagination behavior, or any side effects beyond the role check.

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, front-loaded sentence that conveys the purpose and a key constraint. Every word earns its place; no fluff or redundancy.

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

Completeness3/5

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

There is no output schema, so the description should clarify what the tool returns (e.g., a list of users or a paginated response). It also does not mention error behavior or any other contextual details, leaving the description somewhat incomplete for a tool with six optional parameters.

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?

The input schema has 100% description coverage for all six parameters, with types, defaults, enums, and descriptions. The description only summarizes 'optional filters, pagination, and sorting' without adding any new meaning beyond the schema.

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

Purpose5/5

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

The description clearly states the verb 'List' and the resource 'users from the backend', distinguishing it from sibling tools like list_personas (different resource) and get_usuario_by_email (different operation).

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?

The description mentions the role requirement (ADMIN or MANAGER) but does not explicitly state when to use this tool versus alternatives like list_personas or get_usuario_by_email. Usage is implied rather than clearly contrasted.

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

Deploy Server