Skip to main content
Glama
SVerITG

Metis

by SVerITG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Metis — Update Metis

update_metis

Checks for a newer version and installs it after confirmation, preserving your profile, library, projects, and settings.

Instructions

Check for a newer version of Metis and, with confirm=True, install it.

For installs made by MetisSetup.exe on Windows. Without confirm it only
reports the installed and the newest published version and what updating
does — ask the person before calling again with confirm=True. Updating
keeps their profile, library, projects and settings.

After confirm=True the installer shows a small progress window and stops
Metis while it works, so this conversation loses Metis for a few minutes.
Tell the person: wait until the progress window closes, then quit Claude
Desktop completely (also from the tray) and open it again.

Input Schema

NameRequiredDescriptionDefault
confirmNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv0.1.6

TDQS

A4.9/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and does so: it discloses that updating preserves profile, library, projects and settings, that the installer stops Metis so the session loses the tool for 'a few minutes', and that a progress window appears. It also flags the platform restriction ('installs made by MetisSetup.exe on Windows').

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?

Front-loaded with the core action and the parameter gate, then layered with the platform caveat, the consent rule, and the recovery instructions. Every sentence is actionable, though the final 'tell the person' block is slightly long for what could be a shorter recovery note.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter mutating tool with no annotations, the description covers platform scope, side effects, data preservation, timing, recovery, and consent gating. Return values are handled by the existing output schema, so nothing an agent needs before calling is missing.

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

Parameters5/5

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

The single parameter has 0% schema description coverage, so the description must compensate — and it does, explaining that confirm=True triggers the install while the default (false) only reports versions and consequences. This is more than the schema's bare boolean title conveys.

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?

The first sentence gives a specific verb and resource ('Check for a newer version of Metis and ... install it') and immediately binds the mutating behavior to the confirm=True parameter. That distinguishes it cleanly from siblings like verify_install or metis_doctor, which check installation health rather than version upgrade.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It states exactly when to use each mode: without confirm it is a read-only report, and before calling again with confirm=True the agent must 'ask the person'. It also supplies the post-install user instruction verbatim, leaving no inference about sequencing.

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