Skip to main content
Glama

compile_legal_dossier

Compiles a legal brief or complaint from Markdown into a formal A4 PDF with TOC bookmarks and separator pages, plus an editable Word version.

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.

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": {
      "markdown_content": "<markdown_content>",
      "output_pdf_path": "<output_pdf_path>"
    },
    "name": "compile_legal_dossier"
  }
}

Input 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.1/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the write-but-safe profile is already covered. The description adds real context — output formats, A4 layout, TOC bookmarks for OJV, editable Word delivery — but the internal contradiction ('compila... a PDF' vs 'se entregan en Word, no en PDF') leaves the actual deliverable ambiguous.

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?

Essentially one long sentence with a nested parenthetical, and the trailing 'se entregan en Word, no en PDF' clause introduces confusion rather than clarity. It is not bloated, but the structure is not front-loaded cleanly.

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

Completeness3/5

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

For a six-parameter document generator with no output schema, the description does explain the primary outputs, but omits selection context against siblings, error/overwrite behavior, and how the optional paths (main_pdf_path, mobile_preview_path) relate to the main deliverable.

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 every parameter (title, annexes, main_pdf_path, mobile_preview_path, etc.) is already documented in the schema. The description adds no per-parameter syntax or format detail, so the baseline of 3 applies.

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?

States a specific verb (compila) and resource (escrito judicial/denuncia) plus concrete outputs (A4 PDF with divider covers and TOC bookmarks, editable Word). An agent can grasp the intent, but the description never differentiates this from siblings like generar_documento or export_brief_ojv, and the closing clause muddies what is actually produced.

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

Usage Guidelines2/5

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

No when-to-use guidance, no prerequisites, and no mention of the adjacent document-generation siblings (generar_documento, export_brief_ojv, critique_documento). The agent is left to infer the use case entirely.

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