Skip to main content
Glama
Sign In
devflow

devflow

by cocaxcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

df_rule_create

Create configurable rules to block or warn on Git or Jira actions, preventing unsafe workflow steps.

Instructions

Crear una regla configurable. Las reglas pueden bloquear o advertir sobre acciones.

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>",
      "description": "<description>",
      "scope": "<scope>",
      "action": "<action>"
    },
    "name": "df_rule_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNombre de la regla (ej: no-merge-to-main)
scopeYesAmbito: git, jira, o all
actionYesAccion: block (bloquea) o warn (solo avisa)
descriptionYesDescripcion de lo que hace la regla

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.15

TDQS

A3.7/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden. It does add useful behavioral context by explaining that rules can block or warn about actions. However, it does not disclose potential side effects of creation, authorization requirements, or what happens on success/failure.

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 short sentences with no filler. The primary action 'Crear una regla configurable' is front-loaded, and the second sentence adds relevant context about what rules do.

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 4-required-parameter creation tool with no output schema, the description plus schema is minimally sufficient to invoke it correctly. Still, it lacks any mention of return value, side effects, or setup prerequisites, and the absence of annotations increases the need for such context.

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 all four parameters including enums for scope and action. The description only reinforces the action/enum semantics ('bloquear o advertir') and does not add new parameter-level detail beyond the schema.

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 the specific verb 'Crear' plus the resource 'regla', and clarifies what rules do ('Las reglas pueden bloquear o advertir sobre acciones'). This cleanly distinguishes df_rule_create from sibling operations like df_rule_update, df_rule_list, and df_rule_delete.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies the tool should be used when creating a new rule, which is clear from 'Crear una regla configurable'. However, it gives no explicit guidance about when not to use it or which sibling(s) to prefer (e.g., df_rule_update for modifying an existing rule), leaving the agent to infer the selection logic.

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