delete_custom_rule
Delete a custom rule. Requires API key (Pro+).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Rule ID to delete |
Sunaiva Gate — Agent Rule Enforcement
TDQS
A4/5.0
Behavior3/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
There are no annotations provided, so the description carries the full burden. It discloses the auth/plan requirement, which is useful. However, it does not mention that deletion is permanent or irreversible, nor any side effects, which would be valuable for a destructive operation.
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 sentence, front-loaded with the core action, and contains no redundant or extraneous information. It earns its place efficiently.
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?
Given the low complexity (one required param, no output schema), the description covers the essential context: what it does and the auth requirement. It lacks details on return values or consequences of deletion, but this is acceptable for a simple delete tool.
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 schema description covers 100% of the parameter ('Rule ID to delete'), so the baseline is 3. The description adds no additional meaning beyond what the schema already provides, making it neither exceptional nor deficient.
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 action ('Delete') and the resource ('custom rule'), directly distinguishing it from sibling tools like add_custom_rule, update_custom_rule, and list_custom_rules. It is specific and unambiguous.
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 provides clear context by stating the prerequisite ('Requires API key (Pro+)'), which helps the agent know when the tool can be used. However, it does not explicitly mention when not to use it or suggest alternatives, so it falls short of a full 5.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Try in Browser
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
A3.5/5.0
Disambiguation4/5
Most tools have clearly distinct purposes (e.g., CRUD for custom rules, mode management, presets, validation). However, get_rules, list_custom_rules, and get_rule_modes could be confused since all return rule-related info, though descriptions differentiate their focus.
Naming Consistency5/5
All tool names follow a consistent verb_noun snake_case pattern (e.g., add_custom_rule, get_audit_log, delete_custom_rule). Even multi-word names like ship_confidence_check maintain the pattern, with no mixing of conventions.
Tool Count4/5
16 tools is slightly above the typical 3–15 range but appropriate for the rule enforcement domain, covering custom rules, presets, modes, audit, and validation. However, three planned-but-unimplemented tools add clutter and could be confusing.
Completeness3/5
Core operations are present: full CRUD for custom rules, preset application, mode overrides, validation, and audit log. However, three tools are non-functional (NOT_IMPLEMENTED), and there is no way to remove a bypass or manage constitutional rules, leaving some noticeable gaps.