Skip to main content
Glama

sassy_update_apply

Idempotent

Downloads and stages a specified release asset, verifies its SHA-256 sidecar, and returns the local path plus a manual run command; does not execute the file.

Instructions

Mutating (writes a downloaded file to disk; does NOT execute anything). Downloads one release asset to staging and returns the local path plus a run command the user executes manually. Required: asset_name (exact filename; get valid names from sassy_update_list). Optional tag (default latest) and dest_dir (default LOCALAPPDATA/SassyMCP/updates on Windows, ~/SassyMCP/updates otherwise). A SHA-256 sidecar is required: on mismatch or if no sidecar is published the staged file is deleted and the tool errors. The run command is per asset type AND host OS: msiexec /i for .msi on Windows (.msi is Windows-only and refused with guidance on POSIX), Expand-Archive for .zip on Windows vs unzip -o plus chmod +x on POSIX, tar -xzf for .tar.gz/.tgz, direct path otherwise. Disabled in packaged/frozen builds: returns an error telling you to install a new release artifact instead. Requires network access.

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": {
      "asset_name": "<asset_name>"
    },
    "name": "sassy_update_apply"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagNo
dest_dirNo
asset_nameYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only say readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=true; the description goes far beyond that by disclosing SHA-256 sidecar enforcement, deletion of the staged file on mismatch or missing sidecar, refusal of .msi on POSIX, behavior in packaged/frozen builds, and the network requirement. The per-asset-type and per-OS run commands are exactly the behavioral detail an agent needs before calling.

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 mutating/does-not-execute framing, then required/optional parameters, then the verification and host-OS rules. It is dense and long but nearly every clause is operative; the run-command matrix is the only portion that could be trimmed without losing much.

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?

With no output schema, the description explains what is returned (staged local path plus a run command), what failure modes exist, and what constraints apply. Nothing material for correct invocation is missing for a three-parameter tool.

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?

Schema description coverage is 0%, so the description carries the full burden and does: asset_name is required and must be an exact filename sourced from sassy_update_list, tag defaults to latest, dest_dir defaults to LOCALAPPDATA/SassyMCP/updates on Windows and ~/SassyMCP/updates elsewhere. That supplies meaning the bare schema cannot.

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 specific verb and resource: downloads a release asset to staging, writes it to disk, and returns the local path plus a run command. It also preempts the most likely misreading with 'does NOT execute anything' and points at sassy_update_list for valid asset names, so the agent can distinguish it from the other sassy_update_* siblings.

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?

Clear usage context: use it to stage a release asset when the user will run the install command manually, and use sassy_update_list to obtain a valid asset_name. It does not explicitly contrast against sassy_update_check or sassy_update_changelog, so it stops short of full when/when-not routing.

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