Skip to main content
Glama
rover-001

clenzer

by rover-001
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
register_rulesA

Appends clenzer hygiene rules to AGENTS.md (or CLAUDE.md) in the project root so the agent enforces them every session. Run this once when adding clenzer to a project.

scan_dead_codeA

Scans a TypeScript/JavaScript project for dead code: unused imports, unused variables, and exported functions with no cross-file references. Results are stored in session state for use by cleanse.

scan_complexityC

Scans for unnecessary complexity: overly long functions, deep nesting, large files, and duplicate code blocks.

cleanseA

Safely removes dead code found by scan_dead_code. Auto-removes unused imports and side-effect-free variables. Skips anything risky (functions, exports, initializers with side effects). Always run scan_dead_code first.

reportA

Returns a compact, token-efficient summary of all findings from the last scan. Includes dead code count, complexity hotspots, and actionable next steps.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A3.9/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: scanning for dead code, cleaning dead code, scanning for complexity, reporting, and registering rules. No overlap.

Naming Consistency5/5

All tool names use lowercase with underscores and follow a verb_noun pattern or single verb (cleanse, report). Consistent and predictable.

Tool Count5/5

Five tools is well-scoped for a code hygiene assistant, covering scanning, cleaning, reporting, and setup without excess.

Completeness4/5

Covers dead code detection and removal, complexity scanning, and reporting. Minor gap: no automatic fix for complexity issues (only scan).

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources