Skip to main content
Glama
Sign In
Shannon Lite MCP

Shannon Lite MCP

by dvnold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shannon_get_workspace

Retrieve detailed data for a specific workspace, optionally including raw session JSON, to support workspace management in security workflows.

Instructions

Get detailed data for a single workspace.

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": {
      "workspace": "<workspace>"
    },
    "name": "shannon_get_workspace"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspaceYesWorkspace name.
workspaces_dirNoOptional custom workspace root path.
include_raw_sessionNoInclude raw session.json payload.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.9/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 behavior. It only says 'Get detailed data', but does not specify read-only nature, performance characteristics, or what constitutes 'detailed data'. Lacks disclosure of side effects or limitations.

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?

Single sentence, no fluff. However, it is overly brief; additional detail could improve without harming conciseness. Still efficient for a minimal viable description.

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

Completeness2/5

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

No output schema exists, so the description should explain the return structure. It only says 'detailed data' without any specifics on fields or format. For a tool with 3 parameters and no output schema, this is incomplete.

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 each parameter is documented in the schema. The description adds no extra meaning beyond 'detailed data'. Baseline 3 is appropriate as the schema handles parameter clarity.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool retrieves detailed data for a single workspace, using a specific verb ('Get') and resource ('workspace'). It distinguishes from the sibling 'shannon_list_workspaces' by emphasizing 'single' workspace.

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 guidance on when to use this tool versus alternatives like 'shannon_list_workspaces'. The description does not mention prerequisites, context, or when not to use it, leaving the agent to infer usage.

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