Skip to main content
Glama
Auditor DIAN

Auditor DIAN

by RafaGM1108

Facturas a crédito

facturas_credito
Read-only

Retrieves credit invoices a client received in a date range, with supplier, amount, and due date, so you can answer questions about supplier debt and payment terms.

Instructions

Facturas recibidas con forma de pago a crédito en el periodo, con proveedor, valor y vencimiento.

Úsela cuando el usuario pregunte, por ejemplo:

  • "¿Qué facturas a crédito llegaron en marzo?"

  • "¿Qué le debo a proveedores?" (solo lo que dicen las facturas, no si ya se pagó)

Los eventos (acuse, aceptación, endoso) quedan "por verificar": este servidor no consulta a la DIAN.

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>",
      "desde": "<desde>",
      "hasta": "<hasta>"
    },
    "name": "facturas_credito"
  }
}

Input Schema

NameRequiredDescriptionDefault
desdeYesPrimer día del periodo, AAAA-MM-DD, incluido. Se filtra por fecha de emisión. Bimestre 1 = enero y febrero; 'el año pasado' = 1 de enero a 31 de diciembre.
hastaYesÚltimo día del periodo, AAAA-MM-DD, incluido.
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.1/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 safety is covered. The description adds genuinely non-redundant provenance context: DIAN events (acuse, aceptación, endoso) remain 'por verificar' because the server does not query the DIAN. It does not disclose result volume, ordering, or pagination behavior, which keeps this below a 5.

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 core scope is front-loaded in the first sentence, and the example questions are short and earn their place as disambiguators. The DIAN caveat is relevant but sits after the examples, slightly diluting the front-loading. No filler sentences.

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 three-required-parameter read tool with full schema coverage and no output schema, the description covers purpose, triggers, exclusions, data provenance, and the shape of returned fields. The only material gap is that nothing is said about result size, ordering, or whether long periods are capped.

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 the date format, the 'Bimestre 1 = enero y febrero' convention, and the instruction to resolve razón social via listar_clientes. The description adds no parameter-level meaning beyond that baseline. The mention of 'proveedor, valor y vencimiento' describes returned fields, not inputs.

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 opening sentence names the resource and the discriminating filter precisely: 'Facturas recibidas con forma de pago a crédito en el periodo, con proveedor, valor y vencimiento.' That tells an agent this is a filtered invoice listing scoped to credit payment terms, and the parenthetical '(solo lo que dicen las facturas, no si ya se pagó)' separates it from any payment-status tool. It stops short of naming a sibling (e.g. resumen_periodo, historial_cliente), so sibling routing still requires inference.

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?

It states the trigger conditions with two concrete user-question examples ('¿Qué facturas a crédito llegaron en marzo?', '¿Qué le debo a proveedores?') and adds an explicit boundary: this answers only what the invoices say, not whether they were paid. That is both a when-to-use and a when-not/what-not signal, which is more than most definitions provide.

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