Skip to main content
Glama
Sign In
devflow

devflow

by cocaxcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

df_rule_toggle

Enable or disable a rule by providing its name and a boolean value. Use true to activate or false to deactivate, controlling workflow automation behavior.

Instructions

Activar o desactivar 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>",
      "enabled": "<enabled>"
    },
    "name": "df_rule_toggle"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNombre de la regla
enabledYestrue para activar, false para desactivar

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?

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the core toggle action. It does not mention persistence, idempotence, required permissions, side effects, or what the tool returns after toggling.

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 a single, front-loaded sentence with no filler. It efficiently conveys the core purpose, though it is minimal enough that it could arguably carry more context.

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?

The tool is simple, with only two fully documented parameters and no nested objects, so the schema covers the invocation essentials. However, the absence of annotations and any note about return values or choice vs. df_rule_update leaves the description only minimally viable.

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%: both `name` and `enabled` are already documented. The description adds no new parameter-level meaning beyond restating that the rule is activated or deactivated, so the baseline of 3 is appropriate.

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 ('Activar o desactivar') and the resource ('una regla'), so an agent understands this toggles a rule's enabled state. However, it does not explicitly distinguish this from the sibling df_rule_update, which could also change the enabled field.

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?

No usage context is provided: the description does not explain when to prefer df_rule_toggle over df_rule_update or any other sibling. There are no conditions, exclusions, or alternative routing hints.

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