Tealfabric MCP Server for Cursor

Official

Overview Schema Source Related Servers Discussions Admin

tealfabric_update_process_step

Modify an existing step in a Tealfabric process flow by updating its name, code, sequence, position, schemas, or timeout.

Instructions

Update an existing process step in a process flow.

Input Schema

Name	Required	Description
`name`	No	Step name (preferred)
`step_id`	Yes	Step ID
`language`	No
`sequence`	No
`step_name`	No	Alias for name
`step_type`	No
`position_x`	No
`position_y`	No
`description`	No
`code_snippet`	No
`input_schema`	No
`configuration`	No
`output_schema`	No
`sequence_order`	No
`execution_timeout`	No	Execution timeout in seconds

Schema Changelog

Changes observed during successful MCP inspections.

Changed12 schema fields changedv0.2.0Nov 1, 2026
- 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"
+}
```
- addedInput schema / properties / sequence_order
```
Added value: +{
+  "type": "number"
+}
```
- addedInput schema / properties / step_name / description
```
Added value: +"Alias for name"
```
- removedInput schema / properties / step_status
```
Removed value: -{
-  "type": "string"
-}
```
First observedv0.1.3Aug 30, 2026

TDQS

C2.4/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 behavioral-disclosure burden. It implies a mutation but does not state permissions required, whether the update is partial or full replacement, side effects, reversibility, or how unspecified fields are handled.

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 or redundancy. It is efficient, though it is too thin for a complex 15-parameter mutation tool.

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

Completeness1/5

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

Given 15 parameters, low schema description coverage, nested objects, no annotations, and no output schema, this one-sentence description is not complete enough. An agent would lack critical guidance for invoking the update correctly.

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?

The tool has 15 parameters with only 27% schema description coverage, and the description mentions none of them. It adds no meaning about step_id, aliases like step_name, nested configuration, execution_timeout, or the update semantics of individual fields.

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 gives a clear verb and resource: update an existing process step in a process flow. It is understandable without opening the schema, but it does not distinguish this tool from nearby siblings such as create_process_step, delete_process_step, or update_process.

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?

The description provides no guidance on when to use this tool versus alternatives such as create_process_step, delete_process_step, or update_process. It also omits prerequisites or conditions for updating an existing step.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

tealfabric_update_process_step

Instructions

Input Schema

Schema Changelog

TDQS

Other Tools