workflow-atlas

by claudiu-deving

Overview Schema Source Related Servers Discussions Admin

JavaScript

Local

set_decision

Record a decision answer on a specific step of an algorithm, resolving an open question and persisting the answer.

Instructions

Resolve an open question: record the decision (answer) on a step. 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>",
      "answer": "<answer>"
    },
    "name": "set_decision"
  }
}

Input Schema

Name	Required	Description	Default
`by`	No
`step`	Yes
`answer`	Yes
`algorithm`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Jul 14, 2026

TDQS

C2.7/5.0

Behavior2/5

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

With no annotations, the description bears full burden for behavioral disclosure. It only states 'Persists' and implies mutation ('record the decision'), but fails to disclose idempotency, overwrite behavior, required permissions, or side effects (e.g., invalidates open question status). This is insufficient for safe invocation.

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 that conveys the core purpose efficiently. However, it sacrifices necessary detail; a slightly longer description with parameter clarifications would be more helpful without losing 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 4 parameters, 0% schema coverage, no output schema, and no annotations, the description is far from complete. It does not explain the 'open question' context, how parameters relate, or what happens after invocation. For a tool with this complexity and no other documentation, the description is inadequate.

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?

The input schema has 0% description coverage, yet the description only clarifies 'step' and 'answer' indirectly. It does not explain 'algorithm' (likely an identifier) or 'by' (likely the decider), leaving 50% of parameters semantically opaque. The description adds minimal value beyond the schema.

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 the tool records a decision (answer) on a step to resolve an open question, using specific resources like 'step' and 'decision'. However, it does not differentiate from sibling tools like 'set_workflow_decision' or 'reopen_question', missing an opportunity to clarify its unique scope.

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 (e.g., 'set_workflow_decision' for workflow-level decisions, 'reopen_question' for reopening). No prerequisites or exclusions are mentioned, leaving the agent without decision context.

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