workflow-atlas

by claudiu-deving

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

set_comment

Set or clear a comment on an algorithm step. The comment is saved for later review.

Instructions

Set (or clear, with empty text) a comment on a step of an algorithm. 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>",
      "step": "<step>"
    },
    "name": "set_comment"
  }
}

Input Schema

Name	Required	Description	Default
`step`	Yes
`text`	No
`algorithm`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 14, 2026

TDQS

B3.1/5.0

Behavior2/5

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

No annotations are present, so the description carries full burden. It mentions persistence but lacks details on whether overwrites occur, permission requirements, or side effects. The ability to clear with empty text is noted, but other behavioral traits are missing.

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 short and front-loaded, but it sacrifices essential details. It achieves conciseness at the cost of completeness, making it only adequate.

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 no output schema, no annotations, and 3 parameters, the description is insufficient. It does not explain return values, error states, or what constitutes a valid step. It feels incomplete for practical use.

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

Parameters2/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 minimal value beyond parameter names: algorithm, step (number), text. No explanation of what the step number represents or constraints on text format.

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 clearly states the action: set or clear a comment on a step of an algorithm. It distinguishes from sibling tools by specifying the resource (comment on algorithm step) which is unique among the listed siblings.

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

Usage Guidelines3/5

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

The description implies usage for adding or clearing comments, but does not explicitly state when to use this tool over alternatives like set_decision or set_param. No exclusion criteria or context for selection is provided.

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