Skip to main content
Glama

Evaluador de deuda

evaluar_situacion
Read-onlyIdempotent

El evaluador de deuda de MisCausas.cl: orienta hacia la vía de la Ley 20.720 que corresponde (renegociación, liquidación, reorganización, defensa). Llámalo con las respuestas que ya tengas; si falta una, devuelve la siguiente pregunta con sus opciones para hacérsela a la persona. La orientación es preliminar.

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

Input Schema

NameRequiredDescriptionDefault
perfilNo¿Quién tiene las deudas?
viabilidadNo¿El negocio sigue siendo viable?
montoPersonaNo¿Cuál es el monto total aproximado de tus deudas?
capacidadPagoNo¿Podrías destinar una parte de tus ingresos a un plan de pagos?
tamanoEmpresaNo¿Cuánto vende la empresa al año?
cantidadDeudasNo¿Cuántas deudas tienes impagas por más de 90 días?
objetivoPersonaNo¿Qué buscas principalmente?
procesalEmpresaNo¿Los acreedores ya iniciaron demandas o una solicitud de liquidación forzosa?
procesalPersonaNo¿Te notificaron una demanda ejecutiva, embargo o liquidación forzosa?
primeraCategoriaNo¿Tributaste en primera categoría en los últimos 24 meses?

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, closed-world), the description discloses two behaviors the schema cannot: partial inputs are acceptable and the tool responds with the next missing question plus options, and the answer is 'preliminar' rather than binding legal advice. It does not describe the shape of the final orientation payload.

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?

Three sentences, each doing distinct work: purpose and outcome space first, calling protocol second, caveat last. No repetition of the title or schema content, and nothing extraneous.

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 ten-parameter tool with no output schema, the description covers what matters most: why params are optional, what comes back when data is missing, and that results are preliminary. It could say more about how a complete evaluation is returned, but the essentials for correct invocation are present.

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?

Schema coverage is 100% with enums and Spanish question text for all ten parameters, so the baseline is 3. The description adds the important semantic that these are interview answers to be supplied incrementally rather than a full required set, which explains why zero parameters are required.

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?

Names a specific verb ('orienta') and a specific resource (la vía de la Ley 20.720 que corresponde) and enumerates the four possible outcomes: renegociación, liquidación, reorganización, defensa. An agent can tell instantly this is a legal-path classifier, not a pricing or scheduling tool like its 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 invocation guidance: 'Llámalo con las respuestas que ya tengas' and, if data is missing, relay the returned question to the person. That is a concrete call protocol rather than vague context. It stops short of naming when-not-to-use or alternatives, though the sibling set gives no real competing option.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources