Skip to main content
Glama

vibe_evolution_audit

Audit code evolution across Git snapshots to surface structural duplicate candidates and legacy consumer references, using churn context without automatic deletion or causal claims.

Instructions

Read-only source-based structural duplicate candidates, legacy consumer-reference review, and multi-snapshot code evolution with Git churn; no automatic deletion or causal claims.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "vibe_evolution_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathNoAbsolute path to ONE coding project (prefer its Git repository root), NOT the IDE's application folder or a parent of multiple repositories. When omitted, uses the last successfully assessed project or a recognizable Git/project cwd; otherwise returns project_path_required.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.14

TDQS

C2.8/5.0
Behavior3/5

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

With no annotations present, the description carries the full burden, and it does disclose two valuable traits: read-only operation and the absence of automatic deletion or causal claims. It stops short of permissions, cost/runtime, scope limits across snapshots, or what a result looks like, so meaningful gaps remain for a multi-snapshot analysis tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

It is a single compact sentence with no filler, which is good, but the density is excessive: three stacked capability phrases plus two negations make it hard to parse and it is not front-loaded with an action. A shorter lead clause stating what it produces would earn its place better.

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 read-only analysis tool with no output schema and no annotations, the description conveys the safety posture but not the shape, size, or cost of the result set, nor how the three capability groups relate (one call returning all three, or variants). It is adequate but leaves the agent guessing about output.

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?

There is only one parameter and schema description coverage is 100%, with the schema already explaining the absolute-path constraint, the single-project rule, and the project_path_required fallback. The description adds nothing about the path argument, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names three distinct capabilities (structural duplicate candidates, legacy consumer-reference review, multi-snapshot evolution with Git churn), so an agent can form a rough idea of the resource. But it is a noun-phrase stack with no verb, and 'legacy consumer-reference review' overlaps ambiguously with the sibling vibe_legacy_audit, so it does not cleanly differentiate itself.

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 when-to-use or when-not-to-use guidance is given, and no alternative is named despite several plausible siblings (vibe_legacy_audit, vibe_project_status, vibe_findings). The only routing-adjacent hint is the negation 'no automatic deletion', which is about behavior rather than selection.

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