Skip to main content
Glama
Sign In
workflow-atlas

workflow-atlas

by claudiu-deving
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

reopen_workflow_question

Clears a recorded decision to reopen a workflow question, restoring it as open for reconsideration.

Instructions

Clear a recorded decision so a workflow open question is open again. 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": {
      "sheet": "<sheet>",
      "question": "<question>"
    },
    "name": "reopen_workflow_question"
  }
}

Input Schema

NameRequiredDescriptionDefault
sheetYes
questionYes

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 must disclose behavioral traits. It says 'Persists' implying a permanent state change, but does not mention side effects, reversibility, or authorization needs. 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.

Conciseness2/5

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

The description is very short (13 words), but lacks structure and detail. It is under-specified rather than concise, failing to provide necessary context.

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

Completeness1/5

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

No output schema, no annotations, and no parameter descriptions. The description only covers the high-level action, missing return type, exact effects, and usage context. Incomplete for a tool with zero supporting structured data.

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%, so the description must add meaning for the parameters. It does not explain what 'sheet' or 'question' refer to. The description adds no value beyond the raw schema.

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 uses a clear verb 'Clear' and specific resource 'recorded decision so a workflow open question is open again'. It distinguishes from the sibling tool 'reopen_question' by explicitly mentioning 'workflow open question', indicating a specific context.

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 on when to use this tool vs alternatives like 'set_workflow_decision' or 'reopen_question'. The description does not mention prerequisites or scenarios where this tool is appropriate.

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