Skip to main content
Glama
Sign In
Optimist MCP Server

Optimist MCP Server

by Atomic-Germ
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

find_dead_code

Analyze a file or directory to locate unused code, helping remove dead code and improve maintainability.

Instructions

Identify and locate unused code

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": {
      "path": "<path>"
    },
    "name": "find_dead_code"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesDirectory or file path to analyze

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?

With no annotations, the description carries the full burden of explaining behavior, but it only restates the tool's name-level purpose. It does not disclose whether this is a read-only analysis, how code is traversed, what counts as dead code, or what limitations exist.

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?

The description is extremely concise with no filler or redundant wording. It is slightly too sparse to be fully helpful, but it is appropriately front-loaded and every word earns its place.

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?

For a simple one-parameter analysis tool, the description provides enough to invoke it with a path. However, there is no output schema and no mention of what the tool returns or how results are formatted, which leaves a notable gap in completeness.

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% for the single 'path' parameter, which already documents that it is a directory or file path. The description adds no additional parameter semantics, but the baseline of 3 applies because the schema fully covers the parameter.

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 a specific action — identifying and locating unused code — with a clear target resource. It does not explicitly distinguish itself from sibling tools like detect_code_smells or analyze_dependencies, but the core purpose is evident.

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 choose this tool over siblings or when it should not be used. The description implies a scenario (finding unused code) but offers no exclusions, prerequisites, or comparisons with alternatives.

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