Skip to main content
Glama
Atharva-Jayappa

blast-scope-mcp

assess_command

Split chained shell commands into steps, parse and score each for risk, and return a structured assessment with worst-step severity and recommendation.

Instructions

Assess the blast radius of a shell command.

Splits chained commands on &&, ||, ;, and |, then parses, resolves, and scores each segment independently. The top-level fields surface the worst step's score and recommendation; the chain field contains every step's individual breakdown.

When project_root is provided and no graph database exists yet, the graph is built automatically on the first call. Use index_project to force a rebuild.

Args: command: Raw shell command string to analyze. cwd: Working directory for resolving relative paths. Defaults to the server's current working directory. project_root: Root directory of the project for graph-based scoring. If provided, the graph is auto-built when missing.

Returns: Structured risk assessment with worst-step score, severity, recommendation, and per-step chain breakdown.

Example::

assess_command("cd /tmp && rm -rf .", cwd="/home/user", project_root="/project")

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cwdNo
commandYes
project_rootNo
Behavior4/5

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

Discloses key behaviors: splits chains on separators, resolves paths, scores independently, auto-builds graph when project_root provided. No annotation provided, so description carries full burden; could mention if there are side effects beyond graph building.

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?

Concise yet comprehensive: first sentence states purpose, then details on chain processing, project_root behavior, Args/Returns/Example. Every sentence serves a clear purpose.

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

Completeness5/5

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

Despite no output schema, the description explains return structure (worst-step score, severity, recommendation, per-step chain). Example and parameter details make it complete for agent use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, but description adds rich meaning: command as raw string, cwd for relative path resolution, project_root triggers auto-graph building. Far exceeds schema's types and names.

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 that the tool assesses the blast radius of a shell command, splitting chained commands and scoring each segment. It distinguishes from sibling tools like index_project by focusing on analysis.

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

Usage Guidelines4/5

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

Provides context on when to use (assessing blast radius) and explicitly mentions one alternative (use index_project to force rebuild). Lacks explicit 'when not to use', but example and parameter details guide usage.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Atharva-Jayappa/blast-scope'

If you have feedback or need assistance with the MCP directory API, please join our Discord server