Skip to main content
Glama
Sign In
defluff

defluff

by ahmedak
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

slop_add

Add a phrase to the slop lexicon to flag it in future detections. Use when a user identifies a banned phrase. Supports project or user scope.

Instructions

Add a phrase to the slop lexicon so future detections flag it.

Use when the user says something is slop / a banned phrase. scope='project' (this repo, shared via git) or 'user' (machine-wide).

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": {
      "pattern": "<pattern>",
      "category": "<category>"
    },
    "name": "slop_add"
  }
}

Input Schema

NameRequiredDescriptionDefault
patternYes
categoryYes
scopeNoproject

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.2

TDQS

A4/5.0
Behavior3/5

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

No annotations, so description carries full burden. It discloses that addition flags future detections and explains scope persistence. However, it does not detail side effects like overwriting existing patterns, limits, or reversibility.

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?

Two sentences, each adding value. First states purpose, second gives usage guidance and parameter detail. 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?

For a simple tool with 3 params and no output schema, the description covers purpose, when-to-use, and scope. Lacks details on pattern format or category, but adequate for basic use.

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?

Schema coverage is 0%, but description adds meaning for scope (project vs user). Pattern and category are under-explained. Baseline 3 for minimal compensation.

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 verb 'Add' and resource 'slop lexicon', with the goal of flagging future detections. It distinguishes from siblings 'slop_detect' and 'slop_ignore' by indicating this tool adds rather than detects or ignores.

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?

Explicitly says 'Use when the user says something is slop / a banned phrase' and explains scope options. Does not specify when not to use, but the purpose is clear enough to avoid misuse.

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