Skip to main content
Glama
elpabloultron

Open Legal Chile

by elpabloultron
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Local

compile_legal_dossier

Compile legal briefs from Markdown into a formal A4 PDF with divider covers and TOC bookmarks, plus an editable Word document.

Instructions

Compila un escrito judicial o denuncia en Markdown a PDF formal A4 (carátulas divisorias y marcadores TOC para la OJV) y entrega además el documento de trabajo en Word (.docx, editable): los documentos se entregan en Word, no en PDF.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
titleNoTítulo institucional para los marcadores de navegación TOC (ej. 'Recurso de Protección — Iltma. Corte de Apelaciones')
annexesNoLista de anexos a adjuntar con sus metadatos
main_pdf_pathNoRuta opcional para guardar solo el escrito principal firmado en formato ligero para carga directa en OJV
output_pdf_pathYesRuta de salida para el PDF consolidado con anexos
markdown_contentYesTexto del escrito o informe en formato Markdown
mobile_preview_pathNoRuta opcional para generar versión ligera de lectura para celular

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed7 schema fields changedv1.5.11
    • changedInput schema / properties / annexes / items / properties / desc / description
      Previous value: -"Descripción probatoria del anexo"New value: +"Descripción probatoria y alcance legal"
    • changedInput schema / properties / annexes / items / properties / num / description
      Previous value: -"Ej. 'ANEXO N° 1'"New value: +"Número de anexo (ej. '«ANEXO N.° 1»')"
    • changedInput schema / properties / annexes / items / properties / path / description
      Previous value: -"Ruta al archivo PDF o imagen"New value: +"Ruta al archivo PDF o imagen (.png, .jpg) del anexo"
    • changedInput schema / properties / annexes / items / properties / title / description
      Previous value: -"Título del documento probatorio"New value: +"Título formal del documento probatorio"
    • addedInput schema / properties / main_pdf_path
      Added value: +{
+  "description": "Ruta opcional para guardar solo el escrito principal firmado en formato ligero para carga directa en OJV",
+  "type": "string"
+}
    • changedInput schema / properties / output_pdf_path / description
      Previous value: -"Ruta de salida para el PDF consolidado"New value: +"Ruta de salida para el PDF consolidado con anexos"
    • addedInput schema / properties / title
      Added value: +{
+  "description": "Título institucional para los marcadores de navegación TOC (ej. 'Recurso de Protección — Iltma. Corte de Apelaciones')",
+  "type": "string"
+}
  2. First observedv1.5.1

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full disclosure burden. It does add useful behavioral detail such as A4 formatting, divider covers, TOC markers, and editable .docx output, but it does not disclose side effects, overwrite behavior, permissions, or return values, and it internally contradicts the required output_pdf_path by saying documents are delivered in Word, not PDF.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loaded with the core verb 'Compila', but the tail clause repeats the Word delivery idea and adds contradictory delivery information. It is concise in length but not tightly structured or fully coherent.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool has 6 parameters, no annotations, and no output schema, so the description must explain behavior more completely. It covers the main output concept but omits what happens with optional output paths, what the tool returns, and the inconsistency around PDF vs Word leaves the agent with significant ambiguity.

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%, so the baseline baseline is 3. The description adds some extra meaning by mapping Markdown input to formal PDF/Word outputs, but it does not clarify optional parameters like main_pdf_path or mobile_preview_path beyond what the schema already documents.

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 description states a specific action: compiling a judicial brief or complaint from Markdown into a formal A4 PDF with divider covers and TOC markers, plus an editable Word working copy. It is not a tautology, though it does not distinguish itself from similar siblings like export_brief_ojv, and the final clause claiming documents are delivered in Word, not PDF muddies the stated PDF output.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

The description gives clear context: use this for formatting legal filings for OJV with formal PDF layout and an editable Word version. However, it does not explicitly state when to prefer this tool over alternatives nor what exclusions apply, and the contradictory delivery clause could mislead an agent deciding between PDF and Word outputs.

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