Skip to main content
Glama

critique_documento

Read-only

Auditoría forense de un borrador judicial (5 dimensiones: hecho, derecho, prueba, procedimiento y estrategia, o modo 'goldfish' de revisión contradictoria de contexto cero inspirado en google/elephant-goldfish-model) con el motor de…

Instructions

Auditoría forense de un borrador judicial (5 dimensiones: hecho, derecho, prueba, procedimiento y estrategia, o modo 'goldfish' de revisión contradictoria de contexto cero inspirado en google/elephant-goldfish-model) con el motor de crítica del producto.

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

Input Schema

NameRequiredDescriptionDefault
modoNoModo de auditoría: '5d' (estándar 5 dimensiones) o 'goldfish' (revisor contradictorio de contexto cero sin sesgo de confirmación)5d
textoYesEl borrador a auditar
providerNoProveedor de IA opcional (si se omite, usa el motor local)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.15.0
    • addedInput schema / properties / modo
      Added value: +{
      +  "default": "5d",
      +  "description": "Modo de auditoría: '5d' (estándar 5 dimensiones) o 'goldfish' (revisor contradictorio de contexto cero sin sesgo de confirmación)",
      +  "enum": [
      +    "5d",
      +    "goldfish"
      +  ],
      +  "type": "string"
      +}
  2. Addedv1.11.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds that the critique runs on the product's own critique engine and that provider defaults to a local engine, but with no output schema it never says what the audit response looks like (per-dimension findings, scores, prose).

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?

It is a single sentence with nested parentheses and mixed Spanish/English jargon, which makes it harder to scan than necessary. The verb and resource are front-loaded, but the goldfish aside could be trimmed or split into a clearer clause.

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 three-parameter, single-purpose audit tool with no output schema, the definition covers input modes and engine choice adequately. What is missing is any indication of the returned audit structure, so an agent knows what to expect after invocation.

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% and the schema already documents modo, texto and provider, including the default and the enum semantics. The description's parenthetical adds only provenance ('inspirado en google/elephant-goldfish-model') and the engine reference, so it sits at the baseline for a fully documented schema.

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 (auditoría forense) and resource (borrador judicial) and enumerates the five audit dimensions plus the alternative 'goldfish' mode, so an agent can tell what the tool produces. It does not distinguish this from plausible siblings such as clinica_auditar_borrador or caso_analizar, so it stops short of a 5.

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 two modes are described enough to choose between them ('5d' standard vs 'goldfish' zero-context contrarian review), which is useful usage guidance. However, there is no statement of when to pick this tool over alternative audit/analysis tools, nor any prerequisites or exclusions.

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