Gestion MCP Server

list_personas

Retrieve people from the backend with optional search, pagination, and sorting. Requires authentication with ADMIN, MANAGER, or USER role.

Instructions

List people from the backend with optional search, pagination, and sorting. Requires authentication (ADMIN, MANAGER, or USER 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_personas"
  }
}

Input Schema

Name	Required	Description
`page`	No	Page number (0-based)
`size`	No	Page size
`search`	No	Search term to filter by name or last name
`sortBy`	No	Field to sort by (e.g., nombre, apellidoPaterno, fechaRegistro)
`direction`	No	Sort direction

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 8, 2026

TDQS

A3.6/5.0

Behavior3/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by stating authentication requirements (roles) and implying a read-only list operation. It does not disclose return format, default pagination behavior, or performance implications, but the essential safety and access context is present.

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 extremely concise: two sentences with no redundancy. The first sentence states the core action and optional features, and the second provides the required authentication. Every word earns its place.

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?

Given the five parameters, no annotations, and no output schema, the description covers the purpose, authentication, and key options. It could explicitly mention that the result is a paginated list of persons, but the term 'List people' implies that. The auth requirement is an important contextual addition.

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 already describes all five parameters with 100% coverage, including defaults and constraints. The description only groups them as 'optional search, pagination, and sorting' without adding new semantic detail, thus meeting the baseline of 3 without exceeding it.

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 clearly states the tool's action ('List people') and resource ('from the backend'), along with optional search, pagination, and sorting. However, it does not explicitly distinguish itself from the sibling tool 'list_usuarios' or mention that 'get_persona' serves single-record lookups.

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 provides a clear context for usage by specifying the required authentication roles (ADMIN, MANAGER, or USER). It does not, however, offer guidance on when to prefer this tool over alternatives like 'list_usuarios' or 'get_persona', nor does it exclude specific cases.

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

Deploy Server