Skip to main content
Glama
Auditor DIAN

Auditor DIAN

by RafaGM1108

Cargar facturas de un cliente

ingerir_facturas

Load a client's electronic invoices from a ZIP, XML file, or folder; existing records are skipped to avoid duplicates, and it reports files and documents imported plus reading errors.

Instructions

Carga en un cliente las facturas electrónicas de un ZIP o XML (como llegan por correo) o de una carpeta completa.

Úsela cuando el usuario diga a qué cliente van, por ejemplo:

  • "Carga las facturas de la carpeta 'facturas enero' para Mi Cliente SAS"

Si no dice de qué cliente son, o la carpeta trae facturas de varios clientes, use ingerir_por_cliente. Solo agrega: lo ya cargado se salta y nada se duplica. Devuelve cuántos archivos y documentos entraron y los errores de lectura.

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>",
      "ruta": "<ruta>"
    },
    "name": "ingerir_facturas"
  }
}

Input Schema

NameRequiredDescriptionDefault
rutaYesEl ZIP, XML o carpeta, como lo nombre el usuario: 'facturas enero', 'Descargas/facturas enero' o una ruta completa. Se busca en la carpeta personal, Descargas, Escritorio y Documentos.
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.3/5.0
Behavior4/5

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

Annotations declare a non-readonly, non-destructive, closed-world write, and the description adds real behavior beyond them: the operation is additive only, already-loaded files are skipped, nothing is duplicated, and it returns file/document counts plus read errors. No output schema exists, so disclosing the return shape is valuable. It stops short of mentioning permissions, size limits, or what happens on partial failures.

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-loaded with the core action, then a short example, then the alternative and behavior. The bullet example earns its place by showing the natural-language trigger, though the description is on the longer side for a two-parameter tool.

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?

For a two-parameter ingestion tool with no output schema, it covers the trigger condition, the alternative routing, idempotency guarantees, and the return shape. Missing only edge-case handling such as permissions or what constitutes a read error.

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%, so both parameters are already documented with format details (NIT/cédula variants, search paths for ruta). The description reinforces the context ('como llegan por correo') and the client-scoping requirement but adds little parameter meaning the schema does not already carry — the listar_clientes redirect also appears in the schema.

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?

States a specific verb and resource in the first line ('Carga en un cliente las facturas electrónicas de un ZIP o XML ... o de una carpeta completa'), including the accepted input forms. It is immediately distinguishable from ingerir_por_cliente, which is named explicitly.

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?

Gives an explicit selection rule: use this tool when the user states which client the invoices belong to, with a worked example. It also states the negative condition and the alternative — if no client is given or the folder mixes clients, use ingerir_por_cliente.

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