Skip to main content
Glama
mcgiverdev

MCP API Server

by mcgiverdev

listar-usuarios

Retrieve all registered users from the system for user management and administration tasks.

Instructions

Lista todos los usuarios registrados en el sistema

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The main handler function for the 'listar-usuarios' tool, which fetches users using getUsers and formats them into a text response.
    export async function listUsersToolHandler() {
      // Obtener la lista de usuarios
      const users = await getUsers();
      
      // Formateamos la lista de usuarios para mostrarla
      let usersList = users.map(user => 
        `- ID: ${user.id}\n  Nombre: ${user.nombre} ${user.apellido}\n  DNI: ${user.dni}\n  Creado: ${user.createdAt.toLocaleString()}`
      ).join('\n\n');
      
      // Si no hay usuarios, mostrar un mensaje adecuado
      if (users.length === 0) {
        usersList = "No hay usuarios registrados en el sistema.";
      } else {
        usersList = `Se encontraron ${users.length} usuario(s):\n\n${usersList}`;
      }
      
      // Devolvemos el resultado formateado para MCP
      return {
        content: [
          {
            type: "text" as const,
            text: usersList
          }
        ]
      };
    }
  • Input schema for the 'listar-usuarios' tool, which requires no parameters.
    export const listUsersInputSchema = {};
  • src/main.ts:43-50 (registration)
    Registration of the 'listar-usuarios' tool in the MCP server, linking the name, description, input schema, and handler.
    server.registerTool(
      "listar-usuarios",
      {
        description: "Lista todos los usuarios registrados en el sistema",
        inputSchema: listUsersInputSchema
      },
      listUsersToolHandler
    );
  • Helper function that retrieves all users from the in-memory database, called by the tool handler.
    export async function getUsers(): Promise<User[]> {
      return [...users];
    }
Behavior2/5

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

No annotations are provided, so the description carries full burden for behavioral disclosure. While 'Lista todos' implies a read-only operation, it doesn't specify whether this requires authentication, has rate limits, returns paginated results, or what format the output takes. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 Spanish sentence that directly states what the tool does without any unnecessary words. It's perfectly front-loaded with the core functionality and wastes no space on redundant information.

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?

Given the tool's simplicity (0 parameters, no output schema, no annotations), the description is minimally adequate. It tells the agent what the tool does but leaves important behavioral aspects unspecified. For a list operation with no structured output documentation, more context about return format would be helpful, but the description meets basic requirements.

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

Parameters4/5

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

The tool has 0 parameters with 100% schema description coverage, so the schema fully documents the absence of parameters. The description doesn't need to add parameter information, and it appropriately doesn't mention any parameters. This meets the baseline expectation for a parameterless tool.

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 action ('Lista todos') and resource ('usuarios registrados en el sistema'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'listar-empresas' or 'crear-usuario', but the specificity of 'usuarios' provides implicit distinction. This is clear but lacks explicit sibling differentiation.

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 provides no guidance on when to use this tool versus alternatives. There's no mention of prerequisites, when this tool is appropriate compared to 'crear-usuario' or 'listar-empresas', or any context about filtering or limitations. The agent must infer usage from the tool name and description alone.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mcgiverdev/mcp-api-v1'

If you have feedback or need assistance with the MCP directory API, please join our Discord server