Skip to main content
Glama
Sign In
Shannon Lite MCP

Shannon Lite MCP

by dvnold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shannon_list_workspaces

List all Shannon workspaces with their high-level status. Use optional filters to limit results or specify a custom workspace root path.

Instructions

List Shannon workspaces and their high-level status.

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_list_workspaces"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaces_dirNoOptional custom workspace root path.
limitNoOptional max number of workspace rows.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations provided; description does not disclose read-only nature, pagination, or error behavior. 'List' implies non-destructive but no explicit safety or side effects.

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?

Single sentence, front-loaded with verb, no unnecessary words. Highly concise and structured.

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?

Adequate for a simple list tool with two optional params and no output schema. Could mention return format or that it lists all workspaces, but not required.

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 covers both parameters (workspaces_dir, limit) with descriptions. Description adds no extra meaning beyond schema, so baseline 3.

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 verb 'list', resource 'workspaces', and adds 'high-level status' for specificity. Distinct from siblings like shannon_get_workspace.

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?

Implies use when listing workspaces, but no explicit when-to-use or when-not-to-use versus siblings like shannon_get_workspace. Context can be inferred.

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