Skip to main content
Glama

suite_auto_update

Destructive

Automatically updates the local Open Legal Chile Suite via git pull or pip upgrade, keeping installed legal research tools current and secure.

Instructions

Ejecuta la actualización automática y segura de Open Legal Chile Suite en el entorno local (vía git pull o pip install --upgrade).

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.5.1

TDQS

B3.4/5.0
Behavior2/5

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

The annotations already declare a non-read-only, destructive mutation, and the description partially works against that by branding the operation 'segura' without qualification — yet an upgrade can overwrite local files or installed packages. Beyond naming the mechanism (git pull or pip install --upgrade), it discloses nothing about what gets replaced, whether rollback is possible, permissions required, or failure behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single sentence, front-loaded with the action and target, with the implementation detail tucked into a parenthetical. Nothing is wasted and nothing needs trimming.

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 parameters and no output schema, the description is not obligated to explain returns, but a destructive environment-mutating operation should at least say when it is safe to run and what happens on failure. It covers the mechanism but not the operational contract, so it is minimally adequate rather than complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

There are zero input parameters, so there is no parameter semantics for the description to add; per the baseline this lands at 4. The mention of the two mechanisms is contextual rather than parameter-related, which is appropriate for a no-arg tool.

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 and target: 'Ejecuta la actualización automática ... de Open Legal Chile Suite', and the parenthetical names the concrete mechanism (git pull / pip install --upgrade). This implicitly distinguishes it from a check-only sibling like suite_verificar_actualizacion, but the description never names that sibling, so differentiation is left to inference.

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 by the verb 'actualización': an agent can guess this is the step to run after confirming an update is available. There is no explicit when-to-use vs suite_verificar_actualizacion or suite_instalar, and no stated prerequisites (e.g. clean working tree, network access, installed environment).

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