Skip to main content
Glama
Auditor DIAN

Auditor DIAN

by RafaGM1108

Historial del cliente

historial_cliente
Read-only

Retrieve a registered client's invoice history by NIT or ID to check loaded documents by type and month, first and last issue dates, and upload days with files and errors.

Instructions

Ficha de un cliente registrado: nombre, fecha de registro, cuántos documentos tiene por tipo y por mes de emisión, primera y última fecha de emisión, y cada día en que se cargaron facturas con sus archivos, documentos y errores.

Úsela cuando el usuario pregunte, por ejemplo:

  • "¿Qué tengo cargado de Panadería La Espiga?"

  • "¿Me faltan meses de este cliente?" / "¿Hasta qué fecha tengo facturas?"

  • "¿Cuándo cargué las facturas de marzo?"

No trae montos: para cifras use resumen_periodo.

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": {
      "cliente": "<cliente>"
    },
    "name": "historial_cliente"
  }
}

Input Schema

NameRequiredDescriptionDefault
clienteYesNIT o cédula del cliente, tal como lo escriba el usuario: con puntos, espacios, guion, 'NIT' o 'C.C.', con o sin dígito de verificación. Si lo nombra por su razón social, búsquelo antes con listar_clientes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered; the description adds the valuable negative disclosure that no montos are returned and instead points to resumen_periodo. It also reveals the aggregation granularity (por tipo, por mes de emisión, por día de carga) and that errors are surfaced, which are behavioral traits not visible in the schema. Minor gap: nothing about result size or ordering for a client with many days of carga.

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?

Front-loads the one-line definition with contents, then braces it with example queries and an explicit exclusion. Slightly long: the field enumeration and three quoted example questions could be trimmed without losing routing signal, but every sentence is on-topic and none is filler.

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

Completeness5/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 must describe the return shape – and it does, field group by field group, including the absence of amounts. Combined with the usage triggers and the sibling routing, an agent has everything needed to select and call it correctly.

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?

Schema description coverage is 100% and the schema already explains that the identifier is a NIT or cédula in any user format and that razón social requires listar_clientes first. The description body adds no additional parameter meaning, so the baseline 3 applies – the schema, not the description, carries the parameter semantics.

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?

"Ficha de un cliente registrado" gives a specific resource plus an enumeration of exactly what the ficha contains (nombre, fecha de registro, conteos por tipo y mes, primera/última emisión, días de carga con archivos y errores). It also explicitly distinguishes itself from resumen_periodo ("No trae montos"), so an agent can separate it from the money-summary sibling without reading any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides three concrete user-question triggers ("¿Qué tengo cargado de...?", "¿Me faltan meses?", "¿Cuándo cargué las facturas de marzo?") that map directly onto the tool's content. It also names the alternative for the out-of-scope case ("para cifras use resumen_periodo") and the schema routes razón-social lookups to listar_clientes first.

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