Skip to main content
Glama
Sign In

Mondovo

by com.mondovo.app
OverviewDiscussionsAdmin

Remove a journey step

remove_journey_step
Destructive

Remove a journey step and join its neighbours. The trigger cannot be removed. For a split, ask which path to keep and pass keep_path (yes/no or A/B variant key); all other paths are deleted.

Input Schema

NameRequiredDescriptionDefault
site_idYesThe site, from list_sites
step_idYesA step id exactly as get_journey shows it, e.g. n_email_1
keep_pathNoSplit path to keep: yes, no, or an A/B variant key. Confirm which path the owner wants before deleting the others.
user_goalNoOptional: the user's goal behind this call, in one short sentence of plain words (e.g. "add a page so customers can book tables"). No names, emails or other personal details.
journey_idYesThe journey, by id from list_journeys

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / user_goal
      Added value: +{
+  "description": "Optional: the user's goal behind this call, in one short sentence of plain words (e.g. \"add a page so customers can book tables\"). No names, emails or other personal details.",
+  "type": "string"
+}
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint=true, but the description adds crucial behavioral detail beyond structured fields: neighbouring steps are joined, the trigger is protected, and all non-kept split paths are deleted. It also tells the agent to confirm the owner's intended path before deletion.

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 three compact sentences, front-loads the core action and constraints, and contains no filler.

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

Completeness5/5

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

For a destructive journey-step mutation with full schema coverage and annotations declaring the safety profile, the description supplies the key constraints and split-handling behavior. No output schema exists, but return values are not needed to call it correctly.

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 all parameters are already documented. The description restates keep_path's accepted values and confirmation requirement, which is useful but does not add meaning beyond the schema's own description.

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 states a specific verb and resource ('Remove a journey step'), then adds the immediate structural consequence ('join its neighbours'), which distinguishes it from add_journey_step, move_journey_step, and update_journey_step. It also calls out the trigger exception.

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

Usage Guidelines4/5

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

It gives clear operational guidance: the trigger cannot be removed, and for splits the caller must ask which path to keep and pass keep_path. It does not explicitly name sibling alternatives, but the context for correct invocation is strong.

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

All Mondovo toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources