Skip to main content
Glama
Sign In
workflow-atlas

workflow-atlas

by claudiu-deving
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

delete_algorithm

Delete an algorithm storyboard and its associated review to permanently remove them from the system.

Instructions

Delete an algorithm storyboard and its review. Persists.

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": {
      "algorithm": "<algorithm>"
    },
    "name": "delete_algorithm"
  }
}

Input Schema

NameRequiredDescriptionDefault
algorithmYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

C2.5/5.0
Behavior2/5

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

With no annotations, the description is the sole source of behavioral information. It states the tool deletes both the storyboard and review and that the deletion persists, but lacks details on side effects, error handling, permissions required, or whether deletion is irreversible. Minimal disclosure.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is very short (two sentences) and front-loads the action. However, its brevity sacrifices important details, making it feel under-specified rather than efficiently concise. It earns a middle score.

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 simple delete tool, the description misses key context: what the 'algorithm' parameter should contain, whether the tool is idempotent, what happens if the algorithm doesn't exist, and any cascading effects. Incomplete for safe usage.

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?

Input schema has one string parameter 'algorithm' with no description (0% schema coverage). The tool description does not elaborate on what the parameter represents (e.g., ID, name, path) or its format. Adds no value beyond the parameter name.

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?

Description clearly states the verb 'Delete' and the specific resource 'algorithm storyboard and its review'. It distinguishes from siblings like 'delete_sheet' which targets a different resource type. The action is unambiguous.

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

Usage Guidelines1/5

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

No guidance on when to use this tool versus alternatives. No mention of prerequisites, conditions, or comparison to siblings like 'save_algorithm' or 'get_algorithm'. The description provides no usage context.

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