Skip to main content
Glama
Sign In
Atlas

Atlas

by Ctrl1CandV
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

atlas_save_workflow

Save validated YAML as a workflow file, blocking unsaved changes. New IDs must be free; updates require the previous file hash to prevent silent overwrites.

Instructions

把校验通过的 YAML 保存为 workflows/<workflow_id>.yaml(零成本)。

校验不过不保存。新建要求 id 未被占用;更新必须传 expected_sha256 (上次读到的文件哈希)——文件被改过就拒绝,防静默覆盖。 返回 file_sha256(下次更新用它)与 spec_fingerprint。

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": {
      "workflow_id": "<workflow_id>",
      "yaml": "<yaml>"
    },
    "name": "atlas_save_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
yamlYes
workflow_idYes
expected_sha256No

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.2.0

TDQS

A4.1/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does so well: it discloses that invalid YAML is not saved, that concurrent modification is rejected via expected_sha256 (preventing silent overwrite), and that it is zero-cost. It omits any permission/auth requirements, which keeps it short of a 5.

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?

Front-loads the core action and path, then layers the validation gate, create/update conditions, and return values in short, load-bearing clauses. Minimal waste; the parenthetical '零成本' earns its place.

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

Completeness4/5

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

An output schema exists, yet the description still adds return semantics (file_sha256 reused for next update, spec_fingerprint), which is genuinely useful. Failure modes and concurrency behavior are covered; only auth/permission context is missing.

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

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must compensate. It explains expected_sha256 thoroughly (last-read file hash, optional for create) and implies workflow_id via the file path, but the yaml parameter's content/format is never described.

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?

States a specific verb (save), the exact resource and destination path (workflows/<workflow_id>.yaml), and the precondition that only validated YAML is persisted. An agent can distinguish this from siblings like atlas_validate_workflow or atlas_run_workflow immediately.

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

Usage Guidelines4/5

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

Clearly separates the two usage modes: new creation requires an unoccupied id, while update requires passing expected_sha256. It does not explicitly name atlas_validate_workflow as the prerequisite step, but the '校验通过的 YAML' framing makes the workflow order clear.

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