Skip to main content
Glama

verificar_citas_escrito

Read-only

Checks a draft Chilean legal brief by extracting cited statutes and roles, flagging out-of-range articles and prohibited Common Law figures, and validating citations against BCN.

Instructions

Verificador forense post-redacción: extrae todas las normas legales y roles citados en un borrador mediante citas_legales, detecta artículos fuera de rango y figuras prohibidas de Common Law, y verifica existencia/tenor literal contra BCN.

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": {
      "texto": "<texto>"
    },
    "name": "verificar_citas_escrito"
  }
}

Input Schema

NameRequiredDescriptionDefault
textoYesTexto completo o extracto del escrito judicial o informe a verificar
consultar_bcnNoSi es True, contrasta cada norma citada contra BCN Ley Chile (caché/red)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered; the description adds real behavioral content by disclosing the check pipeline (extraction via citas_legales, range validation, Common Law figure detection, BCN literal-tenor contrast) and that BCN lookup is involved. It does not state what happens when BCN is unreachable or how findings are reported, which would push it higher.

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?

A single front-loaded sentence with a colon-introduced list of exactly the checks performed; every clause carries information and nothing is repeated. It is dense but reads cleanly as a scan of the verification stages.

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?

With no output schema, the description should carry the return shape, and it never says what the verifier produces (per-citation findings, verdicts, whether failures are fatal). For a multi-stage verification tool, the inputs and checks are well covered but the result contract is left implicit.

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 coverage is 100%, so both parameters are already documented, including the consultar_bcn cache/network behavior. The description corroborates that the input is a 'borrador' and that BCN contrast is part of the run, but adds no syntax, size limits, or guidance on when to set consultar_bcn=false.

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 and highly specific resource: forensic post-draft verification of a judicial brief, with the concrete operations spelled out (extract cited norms and roles, detect out-of-range articles, detect prohibited Common Law figures, verify existence/literal tenor against BCN). The 'post-redacción' qualifier alone separates it from pre-drafting citation tools in the sibling set.

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?

The phrase 'post-redacción' establishes the clear lifecycle stage at which to call it, so an agent knows this belongs after a draft exists rather than during drafting or research. It stops short of explicit exclusions or naming a specific alternative tool for the pre-draft case.

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