Skip to main content
Glama
ldap-mcp-server

ldap-mcp-server

buscar_usuario

Search read-only LDAP users by UID, name, or email with partial matching and an optional result limit for focused directory lookups.

Instructions

Busca usuarios por uid, nombre o correo (coincidencia parcial).

Args: texto: Texto a buscar, por ejemplo "garcia" o "ana.". limite: Máximo de resultados (1-100).

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": {
      "texto": "<texto>"
    },
    "name": "buscar_usuario"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoYes
limiteNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden and it does disclose two useful traits: matching is partial/substring rather than exact, and results are capped (1-100). It does not say whether the search is case/accent-insensitive, what ordering results come in, or what an empty result looks like, so mutation/permission-risk context is limited but not contradictory.

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?

One front-loaded sentence carries the purpose and match mode, followed by a tight Args block. Slightly redundant with the parameter titles in the schema, but nothing wasted for a two-parameter tool.

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?

An output schema exists, so return values need not be explained, and the core matching semantics are covered. Still missing for a lookup tool: which field takes precedence when the text could be a uid, name, or email, and whether partial matching applies to all three — an agent could mis-assume behavior.

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?

Schema description coverage is 0%, so the description has to compensate, and it largely does: 'texto' is illustrated with concrete examples ('garcia', 'ana.'), and 'limite' is given the 1-100 bound that the schema omits (schema only shows default 20). It stops short of saying what happens if limite is out of range or if texto is blank.

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?

States a specific verb and resource ('Busca usuarios') plus the searchable fields (uid, nombre, correo) and match semantics (coincidencia parcial). The three siblings are unrelated operations (grupos, cuentas inactivas, cruzar accesos), so no explicit differentiation is needed, but the description never names an alternative.

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 only implied by the name and verb: an agent can infer 'search for a user when you have a partial identifier'. There is no statement of when this is preferable to the siblings, no prerequisites (auth scope needed to see other users), and no guidance on behavior when the text matches nothing.

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