e18e-module-replacements-mcp

scan_dependencies

Scans dependencies from package.json and identifies those with recommended lighter or native alternatives from the e18e project.

Instructions

Scan a list of dependencies (from package.json) and find which ones have recommended replacements from the e18e project

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": {
      "dependencies": "<dependencies>"
    },
    "name": "scan_dependencies"
  }
}

Input Schema

Name	Required	Description	Default
`dependencies`	Yes	A map of package names to versions, like the dependencies field from package.json

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Jul 7, 2026

TDQS

B3.3/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 disclose behavioral traits. It states what the tool does but does not mention permissions, side effects (likely none), error handling, or output format. For a scanning tool, this is minimal transparency.

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?

The description is a single, concise sentence that directly explains the tool's purpose without unnecessary words. Every part adds value, and it is front-loaded with the key action.

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?

Given the tool has one parameter and no output schema, the description is adequate but could be improved. It mentions the input format (from package.json) but does not describe the output structure, which might be important for the agent to understand the result format.

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?

The input schema already describes the parameter as a map of package names to versions, like package.json dependencies. The description adds context about e18e project but does not significantly enhance parameter understanding beyond the schema. With 100% schema coverage, baseline 3 is appropriate.

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 tool scans a list of dependencies (from package.json) and finds recommended replacements from the e18e project. It specifies the verb 'scan', the resource 'dependencies', and the outcome. The sibling tool lookup_replacement implies this tool handles multiple dependencies, distinguishing it effectively.

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?

The description does not provide explicit guidance on when to use this tool versus the alternative lookup_replacement. It only implies that it operates on a list, but no when-to-use or when-not-to-use conditions are stated.

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

Deploy Server