Skip to main content
Glama
Sign In
Shannon Lite MCP

Shannon Lite MCP

by dvnold
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

shannon_read_report

Read a workspace's security assessment report from deliverables to access findings and details.

Instructions

Read a workspace report file from deliverables (defaults to comprehensive_security_assessment_report.md).

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

Input Schema

NameRequiredDescriptionDefault
workspaceYes
workspaces_dirNo
filenameNo
max_charsNoMax characters returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

No annotations exist, so the description carries the burden. It states a read operation (implying non-destructive) and mentions the default filename, but omits error handling, auth needs, 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, no fluff, directly states purpose and default.

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, yet the description fails to specify the return format (e.g., file contents as string) or error scenarios. Tool is a data-returning operation with insufficient return information.

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?

With only 25% schema description coverage, the description adds value by specifying the default filename, but it does not explain workspace, workspaces_dir, or the format of parameters beyond the schema.

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 action ('Read') and the specific resource ('workspace report file from deliverables') with a default filename, distinguishing it from sibling tools like shannon_read_workflow_log.

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 is provided on when to use this tool versus alternatives (e.g., shannon_read_workflow_log for logs). The context lacks explicit context for selection.

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