Skip to main content
Glama

workflow_register

DestructiveIdempotent

Register ordered native-script workflows with run and analysis stages, stage dependencies, and specs so agents can define and execute materials simulation pipelines.

Instructions

Register an ordered native-script workflow. Each stage has id, kind (run/analysis), after IDs and spec. Run spec has run_id; analysis spec has script, inputs, outputs.

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": {
      "task_id": "<task_id>",
      "revision": "<revision>",
      "stages": "<stages>",
      "op_id": "<op_id>"
    },
    "name": "workflow_register"
  }
}

Input Schema

NameRequiredDescriptionDefault
op_idYes
tokenNo
stagesYes
task_idYes
revisionYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the description is not obligated to restate the safety profile. But it adds nothing behavioral: it never explains what the idempotency is keyed on (presumably op_id), what a revision conflict does, whether prior workflow stages are replaced or destroyed, or what token authorizes the call. The content it does provide is structural, not behavioral.

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?

Two sentences, front-loaded with the action and then the data shape, with no filler. It is dense to the point of being terse in places ('after IDs', 'spec'), but every clause carries information.

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?

An output schema exists, so return values need no explanation. But for a destructive, idempotent, four-required-parameter registration tool with zero schema documentation, the description leaves critical gaps: the meaning of revision, the role of op_id in idempotency, and token authorization are all unaddressed.

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 description coverage is 0%, so the description must compensate, and it partially does: it documents the stage shape (id, kind run/analysis, after IDs, spec) and the per-kind spec fields, which is genuinely useful because the schema types 'stages' only as an untyped array of objects. However, four of the five top-level parameters (task_id, revision, op_id, token) get no explanation at all, leaving the compensation incomplete.

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 states a specific verb and resource: 'Register an ordered native-script workflow', and immediately clarifies that stages are ordered and typed. It implicitly distinguishes itself from the artifact/checker/resource register siblings by naming the 'workflow' resource, though it never explicitly contrasts with them.

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?

There is no when-to-use guidance, no prerequisites, and no exclusions or alternatives named. An agent cannot tell from the description whether this supersedes an existing workflow, requires a prior task/revision, or when to prefer a sibling register tool.

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