Skip to main content
Glama

dt_search_doctrina

Read-only

Search and analyze Chile’s Dirección del Trabajo binding labor doctrine by topic or number, with batch review, PDF download, OCR, Markdown conversion, and relevant consideration extraction.

Instructions

Busca dictámenes, pronunciamientos y doctrina laboral vinculante de la Dirección del Trabajo (DT). Permite buscar por materia o número, o analizar dictámenes individuales o en lote (numero/numeros/articleId), descargar PDF oficial, aplicar OCR forense si está escaneado, convertir a Markdown canónico, ingestar en LegalGraphify y desglosar consideraciones relevantes por tema.

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

Input Schema

NameRequiredDescriptionDefault
queryNoMateria o número de dictamen (ej. 'acoso laboral ley karin', 'artículo 161', '344')
numeroNoNúmero u orden de dictamen DT a analizar (ej. 'ORD. N° 344', '129517')
numerosNoLista de dictámenes u ordinarios DT para análisis en lote
tema_relevanteNoPunto laboral controvertido para rankear y citar la doctrina o consideración específica
descargar_formatoNoDescargar el PDF oficial adjunto ('pdf')
convertir_a_md_y_graficarNoConvierte a Markdown canónico e ingesta en el grafo LegalGraphify

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed6 schema fields changedv1.14.0
    • addedInput schema / properties / convertir_a_md_y_graficar
      Added value: +{
      +  "default": false,
      +  "description": "Convierte a Markdown canónico e ingesta en el grafo LegalGraphify",
      +  "type": "boolean"
      +}
    • addedInput schema / properties / descargar_formato
      Added value: +{
      +  "description": "Descargar el PDF oficial adjunto ('pdf')",
      +  "enum": [
      +    "pdf"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / numero
      Added value: +{
      +  "description": "Número u orden de dictamen DT a analizar (ej. 'ORD. N° 344', '129517')",
      +  "type": "string"
      +}
    • addedInput schema / properties / numeros
      Added value: +{
      +  "description": "Lista de dictámenes u ordinarios DT para análisis en lote",
      +  "items": {
      +    "type": "string"
      +  },
      +  "type": "array"
      +}
    • addedInput schema / properties / tema_relevante
      Added value: +{
      +  "description": "Punto laboral controvertido para rankear y citar la doctrina o consideración específica",
      +  "type": "string"
      +}
    • removedInput schema / required
      Removed value: -[
      -  "query"
      -]
  2. First observedv1.5.1

TDQS

B3.1/5.0
Behavior2/5

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

The description adds real behavior beyond the annotations (OCR 'forense' when the document is scanned, canonical Markdown conversion, PDF retrieval), which is valuable. However, it states that the tool 'ingesta en LegalGraphify', i.e. writes into an external graph, while annotations declare readOnlyHint=true; even though this is gated behind the opt-in 'convertir_a_md_y_graficar' flag, the claim conflicts with the safety profile the agent is given. It also says nothing about cost, latency, or what happens to previously ingested content.

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 purpose is front-loaded in the first clause, which is good, but the remainder is a single run-on sentence stacking six distinct capabilities with no grouping or priority. Every capability is real, yet the density makes the mode-switching harder to parse than a short bulleted structure would.

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, zero-required, multi-mode tool with no output schema, the description should clarify what each mode returns and how modes interact. It covers the capabilities but leaves open whether a batch call returns per-document breakdowns, which inputs are mandatory for which mode, and it names a non-existent 'articleId'. Adequate but with clear gaps.

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 is 3 and the schema already explains every parameter including the enum and default. The description adds a little framing ('desglosar consideraciones relevantes por tema' for tema_relevante, batch analysis for numeros), but it also references 'articleId', a parameter that does not exist in the schema, which introduces confusion rather than meaning.

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 names a specific verb and resource ('Busca dictámenes, pronunciamientos y doctrina laboral vinculante de la Dirección del Trabajo') and enumerates the capabilities: search by materia/número, individual or batch analysis, PDF download, OCR, Markdown conversion, graph ingestion. It never distinguishes itself from the close sibling 'doctrina_search' or from 'doctrina_ingestar_documento', whose territory it partly claims, so an agent cannot confidently route between them from the text alone.

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?

Usage is only implied through parameter names: 'Permite buscar por materia o número, o analizar dictámenes individuales o en lote' hints that query vs. numero vs. numeros are alternative modes. There is no explicit when-to-use, no statement of when NOT to use it, no note that modes are mutually exclusive or how to combine tema_relevante with a batch, and no reference to a preferred alternative tool.

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