Skip to main content
Glama
Sign In
Mochi

Mochi

by DevZonayed
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

browser_workflow_delete

Delete a named browser workflow to remove it from the automation system and maintain an organized set of recorded actions.

Instructions

Delete a named workflow.

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>"
    },
    "name": "browser_workflow_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYes
originNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.6/5.0
Behavior2/5

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

With no annotations, the description must fully disclose behavioral traits. It only states 'delete' but does not confirm if the action is permanent, irreversible, or if it requires specific permissions. The lack of detail leaves the AI uncertain about side effects or dependencies.

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 extremely concise at four words. It front-loads the action and object. However, it sacrifices necessary detail; a few more words for parameter context would not harm conciseness.

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?

Given two parameters (one optional) and no output schema, the description should at least explain the 'origin' parameter and confirm the deletion behavior. It lacks completeness for an AI to confidently invoke the tool without additional context.

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 0%, and the description adds no information about the two parameters ('name' and 'origin'). The purpose of 'origin' is entirely unexplained, and 'name' is only inferred as the workflow identifier. The description fails to add meaning beyond the property names.

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 clearly states that the tool deletes a named workflow, using the verb 'Delete' and specifying the resource as 'named workflow'. This differentiates it from sibling tools that export, get, list, run, or save workflows. However, it does not elaborate on what 'named' means or if any identifier format is required.

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?

No guidance is given on when to use this tool versus alternatives, such as whether there is an alternative delete mechanism or if the workflow must exist beforehand. The description does not mention prerequisites, consequences, or when not to delete.

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