Skip to main content
Glama
Sign In
Tealfabric MCP Server for Cursor

Tealfabric MCP Server for Cursor

Official
by tealfabric
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

tealfabric_create_process_step

Create a new process step in a process flow and return the new step_id, enabling you to build and manage workflow steps.

Instructions

Create a new process step in a process flow. Returns the new step_id.

Input Schema

NameRequiredDescriptionDefault
nameNoStep name (preferred)
languageNo
sequenceNo
step_nameNoAlias for name
step_typeNoaction
process_idYesProcess ID to add the step to
descriptionNo
code_snippetNo
input_schemaNo
configurationNo
output_schemaNo
sequence_orderNo
execution_timeoutNoExecution timeout in seconds

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed15 schema fields changedv0.2.0
    • removedInput schema / additionalProperties
      Removed value: -false
    • removedInput schema / properties / assigned_user_id
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / configuration / propertyNames
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / estimated_duration
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / execution_timeout
      Added value: +{
+  "description": "Execution timeout in seconds",
+  "type": "number"
+}
    • addedInput schema / properties / input_schema / propertyNames
      Added value: +{
+  "type": "string"
+}
    • addedInput schema / properties / language
      Added value: +{
+  "enum": [
+    "javascript",
+    "typescript",
+    "php"
+  ],
+  "type": "string"
+}
    • changedInput schema / properties / name / description
      Previous value: -"Alias for step_name"New value: +"Step name (preferred)"
    • addedInput schema / properties / output_schema / propertyNames
      Added value: +{
+  "type": "string"
+}
    • removedInput schema / properties / position_x
      Removed value: -{
-  "type": "number"
-}
    • removedInput schema / properties / position_y
      Removed value: -{
-  "type": "number"
-}
    • addedInput schema / properties / sequence_order
      Added value: +{
+  "type": "number"
+}
    • changedInput schema / properties / step_name / description
      Previous value: -"Step name"New value: +"Alias for name"
    • removedInput schema / properties / step_status
      Removed value: -{
-  "type": "string"
-}
    • changedInput schema / required
      Previous value: -[
-  "process_id",
-  "step_name"
-]New value: +[
+  "process_id"
+]
  2. First observedv0.1.3

TDQS

C2.6/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. It discloses only the return value; it says nothing about where the new step is placed by default, how sequence/sequence_order conflicts are resolved, whether required fields like step_type default to 'action', or what permissions are needed for a mutation.

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?

Two short sentences with the purpose front-loaded and zero filler. It is efficient, though the terseness tips into under-specification for a 13-parameter tool.

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

Completeness2/5

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

For a mutation tool with 13 params, nested object schemas, alias/duplicate fields, and no annotations, two sentences are far from sufficient. The stated return value partially helps since there is no output schema, but the parameter ambiguity and placement behavior are unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is only 31% across 13 parameters including nested objects, and the description mentions none of them. Critical ambiguities — the 'name' vs 'step_name' alias and the 'sequence' vs 'sequence_order' duplicate — are left completely unexplained, so the description compensates for nothing.

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?

States a specific verb and resource ('Create a new process step') plus the return value ('new step_id'), which is enough to distinguish it from tealfabric_update_process_step and tealfabric_delete_process_step. It does not, however, explain what a process step is or how it relates to the sibling process tools.

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 versus tealfabric_update_process_step or tealfabric_create_process, no prerequisite that the parent process must already exist, and no note about ordering relative to other steps. The agent is left to infer all of this.

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