Skip to main content
Glama
Auditor DIAN

Auditor DIAN

by RafaGM1108

Diagnóstico para soporte

diagnostico
Read-only

Collects version, data folder, plugins, per-client upload status, and recent read warnings to diagnose Auditor DIAN issues and create a shareable report without invoice amounts or content.

Instructions

Estado de la instalación para reportar un problema: versión, carpeta de datos, plugins y, por cliente, documentos, archivos cargados, última carga y advertencias de lectura (las últimas 20). No incluye montos ni contenido de las facturas, así que se puede compartir.

Úsela cuando el usuario diga, por ejemplo:

  • "Algo no funciona" / "No me cargó una factura" / "Una cifra no me cuadra"

  • "Dame el diagnóstico de Auditor DIAN"

Explique en palabras sencillas lo que encuentre y, si hay que reportarlo, entréguele el resultado completo para que lo copie.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.1

TDQS

A4.2/5.0
Behavior3/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 does add useful context beyond that: the output is bounded to the last 20 reading warnings, contains no monetary or invoice content, and is therefore safe to share with the user.

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 with the payload summary, then a short bulleted list of trigger phrases, then a one-line handling instruction. Every sentence earns its place and nothing is redundant.

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?

With no output schema and no parameters, the description carries the full burden of describing the return, and it enumerates the returned fields plus the 20-item cap well. It could be slightly more explicit about the shape or size of the payload, but an agent has enough to call it correctly.

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?

The tool takes zero parameters, so there is no parameter semantics to explain; baseline of 4 applies. The description correctly never implies any inputs are needed.

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 precise verb+resource: reports the state of the installation (version, data folder, plugins, per-client documents, uploaded files, last upload, and reading warnings for the last 20). It also bounds the scope by declaring what is NOT included (amounts and invoice contents), so an agent can immediately tell it apart from document-listing or reporting siblings.

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 explicit trigger contexts with quoted example utterances ("Algo no funciona", "No me cargó una factura", "Dame el diagnóstico de Auditor DIAN") and tells the agent how to present results. It does not name any alternative tool or state when to prefer a sibling such as listar_clientes or buscar_documentos, which keeps it short of a 5.

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