Skip to main content
Glama

caso_analizar

Read-only

Analyze Chilean case files, folders, or text to return a plan: matter, tools and order, and missing information.

Instructions

Usala SIEMPRE que la persona pida analizar un caso, una carpeta de expediente, un expediente, unos documentos o 'este caso', aunque no nombre ninguna herramienta: frases como «¿podés analizar esta carpeta?», «analizame el caso de Ailin», «¿por dónde empiezo con esto?» o «mirá estos documentos y decime de qué se trata» son exactamente su entrada. Devuelve un PLAN: de qué se trata, qué herramientas usar y en qué orden, y qué falta para poder avanzar. No modifica nada ni consulta servicios externos: sólo lee lo que le pasás. La materia la decide con reglas (Rol/RIT y palabras clave chilenas), no adivinando; si no alcanza la información, lo dice.

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": {
      "entrada": "<entrada>"
    },
    "name": "caso_analizar"
  }
}

Input Schema

NameRequiredDescriptionDefault
tipoNocómo interpretar la entrada (por defecto se deduce)
entradaYesruta de la carpeta o del archivo, o el texto mismo
consultaNola pregunta u objetivo, para que el plan apunte a eso
estudio_completoNoSi es True, realiza en un solo paso local el análisis, consulta de marco normativo BCN y doctrina FTS5, consolidando la respuesta sin turnos adicionales
generar_dashboardNoSi es True, genera un dashboard HTML autónomo e interactivo con LegalCanvas (SVG, checklist y citas)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.12.0
    • addedInput schema / properties / generar_dashboard
      Added value: +{
      +  "description": "Si es True, genera un dashboard HTML autónomo e interactivo con LegalCanvas (SVG, checklist y citas)",
      +  "type": "boolean"
      +}
  2. Changed1 schema field changedv1.6.5
    • addedInput schema / properties / estudio_completo
      Added value: +{
      +  "description": "Si es True, realiza en un solo paso local el análisis, consulta de marco normativo BCN y doctrina FTS5, consolidando la respuesta sin turnos adicionales",
      +  "type": "boolean"
      +}
  3. Addedv1.6.4

TDQS

A3.7/5.0
Behavior2/5

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

Annotations already declare readOnlyHint/true, destructiveHint/false and openWorldHint/true, and the description usefully adds that it only reads supplied input and that materia is classified by deterministic rules (Rol/RIT + keywords) with an explicit 'no alcanza la información, lo dice' failure mode. However, the blanket claim 'no consulta servicios externos' conflicts with openWorldHint=true and with its own estudio_completo parameter, which performs BCN normativa and FTS5 doctrine lookups – a materially misleading capability statement for an agent deciding whether to call it.

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 trigger rule and example utterances, then the deliverable, then behavioral limits – a sensible priority order. It is somewhat wordy (many quoted sample phrases), but each sentence carries routing or expectation-setting value.

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, the description compensates by spelling out the shape of the returned PLAN, which is exactly what an agent needs to sequence follow-up tools. It omits the relationship to caso_ejecutar and under-describes the external-call behavior of estudio_completo, but for a 5-param read-only planner it is close to sufficient.

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% across all five parameters, so tipo, entrada, consulta, estudio_completo and generar_dashboard are already documented in structured data. The description adds nothing parameter-specific (it does not mention estudio_completo, generar_dashboard, or the tipo enum), so the baseline 3 applies.

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?

The description names a specific action (analizar) and resource (caso/carpeta/expediente/documentos) and states precisely what the tool returns: a PLAN covering qué se trata, qué herramientas usar y en qué orden, y qué falta. That plan-vs-execution framing implicitly separates it from caso_ejecutar without needing to open either schema.

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?

Trigger guidance is unusually explicit – 'Usala SIEMPRE que la persona pida analizar un caso... aunque no nombre ninguna herramienta', backed by four example utterances that cover the common phrasings. It lacks an explicit when-not clause or a named alternative (e.g. route to caso_ejecutar once the plan is defined), so it stops 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.

Deploy Server

Other Tools