Skip to main content
Glama
ldap-mcp-server

ldap-mcp-server

detectar_cuentas_inactivas

Detect inactive LDAP accounts by listing expired users or those whose password has not changed within a configurable number of days for security audits.

Instructions

Lista cuentas expiradas o con la clave sin cambiar en más de N días.

Args: dias_sin_cambio_clave: Umbral en días (por defecto 90).

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

Input Schema

NameRequiredDescriptionDefault
dias_sin_cambio_claveNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral-disclosure burden. It implies a read-only listing operation, but does not state permissions, whether it is safe, how results are formatted, or whether there are rate limits.

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?

The description is short and front-loaded, stating the purpose before the parameter details. The Args section is somewhat redundant for a single parameter but does not add verbosity or bury the key 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?

For a simple single-parameter query tool, the description gives enough to invoke it correctly. However, with no annotations and no output schema, it leaves open the read-only nature, return format, and any operational constraints.

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 must explain the sole parameter, and it does: dias_sin_cambio_clave is the threshold in days with a default of 90. This fully compensates for the otherwise undocumented schema property.

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 and resource: it lists accounts that are expired or whose password has not changed in more than N days. This is clear enough to distinguish it from siblings like buscar_usuario or listar_grupos_de_usuario, although it does not explicitly name those alternatives.

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 explains what the tool returns but gives no explicit guidance on when to choose it over alternatives such as buscar_usuario or cruzar_accesos. There are no stated prerequisites, exclusions, or contextual cues beyond the basic criteria.

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