Skip to main content
Glama
Auditor DIAN

Auditor DIAN

by RafaGM1108

Cargar facturas y repartir por cliente

ingerir_por_cliente

Load multiple client invoices at once, routing each file to the buyer named on that invoice. Use it when users ask to upload or distribute downloaded invoices by client.

Instructions

Carga facturas de varios clientes a la vez: cada archivo va al cliente que aparece como comprador en la factura.

Úsela cuando el usuario diga, por ejemplo:

  • "Carga mis facturas" / "Ya descargué las facturas, cárgalas" (sin ruta)

  • "Reparte por cliente las facturas de la carpeta 'correo noviembre'"

Solo carga en clientes ya registrados. clientes_no_creados trae el NIT y el nombre de los compradores sin registrar: muéstreselos al usuario, pregunte si los crea (crear_cliente) y vuelva a llamar; lo ya cargado no se duplica. sin_asignar lista archivos que no son facturas legibles o traen varios compradores, con el motivo.

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

Input Schema

NameRequiredDescriptionDefault
rutaNoCarpeta, ZIP o XML como lo nombre el usuario. Omítala si no dice dónde están: se revisa la carpeta de Descargas.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.1/5.0
Behavior5/5

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

Goes well beyond the annotations: it discloses idempotency (already-loaded files are not duplicated), the restriction to registered clients, and the meaning of two result buckets (clientes_no_creados with NIT and name, sin_asignar with reasons such as unreadable or multi-buyer files). With no output schema present, naming these return fields is exactly the behavioral context an agent needs, and the no-duplication guarantee is consistent with destructiveHint=false.

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?

Front-loaded one-sentence summary, then bulleted user phrasings that directly support tool matching, then the constraints. Every sentence carries selection or behavior information; nothing is padding.

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 mutating, one-optional-parameter tool with no output schema, the description covers prerequisites, idempotency, and failure buckets well. It leaves minor gaps: what a fully successful run returns, and any limits on batch size or supported file types beyond the implicit 'facturas legibles'.

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 coverage is 100% and the single optional parameter already documents that omitting it falls back to the Downloads folder. The description reinforces this through the pathless example utterance but adds no new format or syntax detail, so the baseline of 3 applies.

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 plus the defining behavior: it loads invoices from multiple clients at once and routes each file to the buyer named on the invoice. That routing rule distinguishes it functionally from a plain invoice-ingestion sibling, though no sibling 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 Guidelines4/5

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

Gives concrete triggering utterances ("Carga mis facturas", "Reparte por cliente las facturas de la carpeta 'correo noviembre'"), including the no-path case, which is unusually actionable. It also states the prerequisite that clients must already exist and prescribes a recovery path via crear_cliente plus a retry, but never says when to prefer ingerir_facturas instead.

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