Skip to main content
Glama
Sign In
devflow

devflow

by cocaxcode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

df_flow_create

Create automated workflows with a trigger and steps. The AI executes the flow when user input matches the trigger.

Instructions

Crear un nuevo flow (playbook) con nombre, disparador y pasos. El AI lo ejecuta cuando el usuario dice algo que matchea el trigger.

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>",
      "trigger": "<trigger>",
      "steps": "<steps>"
    },
    "name": "df_flow_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesNombre del flow (ej: pr-ready)
stepsYesPasos del flow: [{tool, confirm?, target?, note?}]
triggerYesDescripcion del disparador (ej: cuando el usuario dice "PR listo")

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 must carry the behavioral burden. It discloses the auto-execution behavior (the AI runs it when trigger matches), which is valuable. However, it omits other behavioral details such as idempotency, overwrite behavior, or error conditions.

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 concise sentences. The purpose is front-loaded, and the behavioral note about trigger execution is added without unnecessary fluff. Every word contributes value.

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?

With 3 required parameters fully described in the schema and a concise description covering purpose and auto-execution, the tool is largely usable. However, it lacks details on error handling, idempotency, or what happens if a flow with the same name exists, which would be helpful for safe invocation.

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 coverage is 100% – all three parameters (name, trigger, steps) have descriptions. The description only restates these parameter names without adding new semantics or examples beyond what the schema already 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 clearly states the verb 'Crear' (create) with the resource 'flow (playbook)' and lists the key attributes (name, trigger, steps). It also explains the tool's role in the system (executed when trigger matches), which distinguishes it from sibling tools like df_flow_update or df_flow_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 creation but does not explicitly contrast with alternatives like df_flow_update or df_flow_delete. It mentions the trigger execution context, which gives some situational guidance, but lacks explicit when-to-use/when-not-to-use language.

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