Skip to main content
Glama
cuttalo

DepScope

by cuttalo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

find_alternatives

Read-onlyIdempotent

Find curated replacements for deprecated or unhealthy packages across 17 ecosystems. Returns alternative names, reasons, and standard library built-ins.

Instructions

Curated replacements for deprecated/unhealthy packages, including stdlib built-ins (e.g. fs.rm for rimraf). USE WHEN: pkg flagged AVOID/URGENT; 'what to use instead of X'; before guessing a replacement name. RETURNS: {alternatives[]: {name, reason, is_stdlib}}.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ecosystemYes
packageYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, and non-destructive hints. The description adds 'curated' (not live, likely authoritative) and shows the output structure, contributing to transparency without contradicting annotations.

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 three concise, purposeful sentences: definition, use cases, output format. It is front-loaded and every sentence adds value, with no redundancy.

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

Completeness4/5

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

The description covers purpose, usage, and return shape, which is sufficient for a simple lookup tool. However, parameter semantics and potential edge cases (e.g., no alternatives found) are not addressed, leaving slight gaps.

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

Parameters2/5

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

Schema description coverage is 0%, and the description does not explain the parameters. The term 'package' is implied by the purpose, but 'ecosystem' is never mentioned. The schema enum helps, but the description provides no added meaning.

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 a specific verb and resource: 'Curated replacements for deprecated/unhealthy packages'. It also includes an example and distinguishes itself from sibling tools by focusing on alternatives rather than checks or scans.

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?

The description provides explicit 'USE WHEN' conditions (pkg flagged AVOID/URGENT, asking for replacements, before guessing), but it does not mention when not to use it or name alternative sibling tools. This is clear context without exclusions.

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