Skip to main content
Glama

invocar_herramienta

Read-only

Executes a discovered Open Legal Chile tool by exact name with JSON arguments, enabling agents to run catalogued legal queries after tool discovery.

Instructions

Invoca dinámicamente cualquier herramienta del catálogo completo de Open Legal Chile tras localizarla con descubrir_herramientas (útil en OPENLEGAL_PROFILE=router).

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": {
      "nombre": "<nombre>"
    },
    "name": "invocar_herramienta"
  }
}

Input Schema

NameRequiredDescriptionDefault
nombreYesNombre exacto de la herramienta MCP a ejecutar
argumentosNoDiccionario JSON con los parámetros de la herramienta

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.16.0

TDQS

A3.8/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 ostensibly covered. The description adds the discovery prerequisite and the router-profile context, but says nothing about what happens with an unknown tool name, whether the target tool's raw result or an error is returned, or that `argumentos` must conform to the target tool's own schema. For a generic dispatcher these omissions matter.

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 no filler; the verb-plus-scope comes first and the prerequisite follows. The parenthetical env-var reference is opaque to an agent that cannot read `OPENLEGAL_PROFILE`, so a small amount of wording is spent on something not actionable.

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 nested-parameter, free-form dispatcher with no output schema, the definition covers the one thing an agent must know (locate first, then pass name plus args) and nothing more. It leaves error behavior, result shape, and side-effect risk unstated, which is thin but arguably minimum viable given the 100%-covered input schema.

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 `nombre` (exact MCP tool name) and `argumentos` (JSON dict of parameters) are already documented, and the description adds only the implied point that the arguments belong to the target tool. Baseline 3 applies: the description does not add pass-through semantics, validation behavior, or a concrete example for the free-form nested object.

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?

States a precise verb (invoca dinámicamente) and an exhaustive resource scope ('cualquier herramienta del catálogo completo de Open Legal Chile'), and implicitly separates itself from the discovery sibling by making `descubrir_herramientas` a prerequisite rather than a substitute. An agent can tell this is the execution/dispatch step, not a search step, without opening either schema.

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?

Gives a clear trigger sequence: first locate the tool with `descubrir_herramientas`, then invoke it here, and flags the `OPENLEGAL_PROFILE=router` context where this path is relevant. It stops short of saying when NOT to use it, i.e. whether a directly named sibling should be called instead outside router mode, so the routing decision is only partly resolved.

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