Skip to main content
Glama
Sign In
Shannon Lite MCP

Shannon Lite MCP

by dvnold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shannon_stop

Stop Shannon worker and infrastructure containers. Optionally clean up volumes and network by providing the required confirmation token.

Instructions

Stop Shannon worker and infra containers. Clean mode requires a confirmation token.

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

Input Schema

NameRequiredDescriptionDefault
cleanNoAlso remove Shannon volumes/network.
confirm_destructiveNoRequired for clean mode: I_UNDERSTAND_THIS_WILL_REMOVE_SHANNON_DATA

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior2/5

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

No annotations are provided, so the description must convey behavioral context. It only mentions stopping containers and a destructive clean mode, but lacks details on permissions, impact on running processes, or atomicity.

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 front-load the main action and immediately address the dependent parameter requirement.

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?

For a straightforward stop action, the description covers the core functionality and clean mode caveat, though it omits whether the stop is forceful or graceful.

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?

Both parameters are documented in the schema with descriptions; the description adds no new meaning beyond what the schema already provides.

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 description clearly states the verb 'Stop' and the resource 'Shannon worker and infra containers', precisely distinguishing it from sibling tools that deal with configuration, health, status, or starting scans.

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?

The description implicitly indicates usage for stopping, but provides no explicit guidance on when to choose this tool over alternatives or any prerequisites.

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