Skip to main content
Glama
Sign In
devflow

devflow

by cocaxcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

df_rule_delete

Delete a named rule to remove it from your workflow, eliminating outdated or incorrect automation settings.

Instructions

Eliminar una regla.

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": {
      "name": "<name>"
    },
    "name": "df_rule_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNombre de la regla a eliminar

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.15

TDQS

C2.9/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It only repeats the deletion action implied by the tool name and does not warn that deletion is likely irreversible, affect rule project overrides, or remove associated configurations. Some credit is given because 'eliminar' does clearly signal 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.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely brief with no filler or redundant content. It is front-loaded as a direct action phrasecars, though the brevity also contributes to the lack of usage and behavioral guidance.

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

Completeness3/5

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

For a one-parameter deletion tool with full schema coverage, the description plus schema technically provides enough information to invoke it. However, it lacks context about what deletion entails, possible side effects, or how it differs from toggling or updating a rule. This is adequate but clearly incomplete.

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?

Input schema coverage is 100%: the single required parameter 'name' is already described as the name of the rule to delete. The description adds no additional parameter semantics, which is acceptable given that this is a minimal one-parameter tool.

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 'Eliminar una regla' clearly identifies the operation as deleting a ruleeb, distinguishing it from sibling tools like df_rule_create, df_rule_update, and df_rule_toggle. It uses a specific verb and resource, though it does not add any extra scoping or differentiation text.

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?

There is no guidance on when to use this tool versus other rule-related tools such as df_rule_update or df_rule_toggle. The description does not state prerequisites, exclusions, or consequences, so an agent must infer usage solely from the tool name and schema.

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