Skip to main content
Glama
Sign In
Shannon Lite MCP

Shannon Lite MCP

by dvnold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shannon_uninstall

Stop the Shannon runtime and delete the ~/.shannon directory with a required confirmation token to prevent accidental data loss. Optionally remove Shannon volumes and network.

Instructions

Stop Shannon runtime and remove ~/.shannon. Requires explicit confirmation token.

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": {
      "confirm_destructive": "<confirm_destructive>"
    },
    "name": "shannon_uninstall"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirm_destructiveYesRequired token: DELETE_SHANNON_HOME_AND_STOP_SHANNON
cleanNoAlso remove Shannon volumes/network while stopping.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

No annotations provided. Description explicitly states the destructive action (stop runtime and remove home directory) and mentions the confirmation token. Lacks details on how 'clean' affects volumes/network and post-uninstall state, but adequately discloses core 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?

Two concise sentences with no unnecessary words. Information is front-loaded: action, target, precondition.

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

Completeness4/5

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

Given no output schema, the description covers the main purpose and prerequisites. It could mention expected outcome or return format, but for a destructive uninstall tool, the current level is adequate.

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 the description adds little beyond what the schema already provides. It reinforces the confirmation token requirement, but that is already in the schema. Baseline 3 is appropriate.

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?

Description clearly states the verb 'Stop' and resource 'Shannon runtime' and 'remove ~/.shannon'. It distinguishes from siblings like shannon_stop which likely only stops without removal.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool versus alternatives like shannon_stop. The only hint is the requirement for a confirmation token, which is not a usage context but a precondition.

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