Skip to main content
Glama
Sign In
controld-mcp

controld-mcp

by SwaggyMike
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Delete custom rules

delete_rules
Destructive

Delete DNS rules by exact hostname or wildcard pattern with a mandatory confirmation flag to prevent accidental removal.

Instructions

Delete rules by exact hostname. This is destructive and requires confirm=true.

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": {
      "profile": "<profile>",
      "hostnames": "<hostnames>",
      "confirm": "<confirm>"
    },
    "name": "delete_rules"
  }
}

Input Schema

NameRequiredDescriptionDefault
confirmYesMust be exactly true after reviewing the requested change
profileYesExact profile name or profile ID
hostnamesYesExact domains or *.domain wildcard patterns

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description's 'this is destructive' is redundant with structured data. The confirm requirement is also already encoded as const true in the schema. The 'exact hostname' phrase adds some behavioral context, though the schema already clarifies exact domains/wildcards. No annotation contradiction exists.

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 two short sentences with the purpose front-loaded. 'This is destructive and requires confirm=true.' is concise and directly relevant, with no filler or unnecessary wording.

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 deletion tool with full schema coverage and destructive annotations, the description covers the essential points: what it deletes, the matching key, and the confirmation requirement. It could be slightly more explicit about wildcard support or which rule types are deleted, but the title and schema largely cover those gaps.

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 description coverage is 100%, so the schema already documents profile, hostnames, and confirm. The description only restates 'by exact hostname' and the confirm requirement, adding minimal semantic value beyond what the input schema provides.

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 uses a specific verb and resource ('Delete rules') and adds a key qualifier ('by exact hostname'). The title 'Delete custom rules' reinforces the scope, and this clearly distinguishes the tool from sibling tools like create_bypass_rules, create_block_rules, and list_profile_rules.

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 clearly implies when to use the tool: when you need to delete custom rules. It also adds a caution about destructiveness and confirmation, but it does not explicitly mention alternatives or exclusions such as pause_profile or create_* rules.

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