Skip to main content
Glama
Sign In
Deslop MCP Server

Deslop MCP Server

by collin-ho
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

deslop_diff

Analyze git diff changes to detect AI-generated code slop patterns like redundant comments and verbose logging for cleaner code.

Instructions

Analyze only changed files from git diff for slop patterns

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": "deslop_diff"
  }
}

Input Schema

NameRequiredDescriptionDefault
stagedNoIf true, analyze staged changes only

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies analysis of 'slop patterns' but doesn't specify what that entails, whether it's read-only or has side effects, or any constraints like permissions or rate limits. This is a significant gap for a tool with potential mutation implications.

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, efficient sentence that directly states the tool's purpose without unnecessary words, making it appropriately sized and front-loaded for quick understanding.

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

Completeness2/5

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

Given the lack of annotations and output schema, the description is incomplete. It doesn't explain what 'slop patterns' are, what the analysis entails, or what results to expect, leaving gaps in understanding the tool's behavior and output for a potentially complex operation.

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 has 100% coverage with one parameter ('staged') fully described. The description doesn't add any parameter-specific details beyond what the schema provides, so it meets the baseline of 3 for high schema coverage without extra value.

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 the action ('Analyze') and the target ('changed files from git diff for slop patterns'), making the purpose understandable. However, it doesn't explicitly differentiate from sibling tools like 'deslop_analyze' or 'deslop_fix', which likely have related purposes, so it misses full sibling distinction.

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 provides minimal context by specifying 'changed files from git diff', but it offers no guidance on when to use this tool versus alternatives like 'deslop_analyze' or 'deslop_fix', nor does it mention prerequisites or exclusions, leaving usage unclear.

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