Skip to main content
Glama

自動化仕様書の下書き

draft_automation_spec
Read-onlyIdempotent

Draft a ten-section automation specification from existing steps, marking human approval gates and automation candidates. No actions are executed. 現行手順から承認箇所を明示した仕様書の下書きを作成します。

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_name": "<task_name>",
      "current_steps": "<current_steps>"
    },
    "name": "draft_automation_spec"
  }
}

Input Schema

NameRequiredDescriptionDefault
frequencyNo
task_nameYes
owner_roleNo
tools_usedNo
current_stepsYes

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description contributes beyond that by clarifying that no actions are executed and that the draft explicitly marks human approval gates and automation candidates — meaningful behavioral content about what the output contains.

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 core action and the no-execution caveat, with no filler. The Japanese sentence largely mirrors the English, which is reasonable for a bilingual title but does not add new information.

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

Completeness3/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-value explanation is unnecessary, and the read-only nature is well covered. However, for a five-parameter generator with zero schema description coverage, the definition leaves an agent without guidance on how the non-step inputs affect the draft.

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% across five parameters, so the description carries the full burden, yet it only alludes to one of them ("existing steps" for current_steps). The roles of task_name, frequency, owner_role and tools_used — and especially how they shape the ten sections — are not explained anywhere.

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 gives a specific verb and artifact ("Draft a ten-section automation specification from existing steps") and even states the output structure's size. It does not reference the sibling tools, so an agent cannot tell from the text alone why it would choose this over estimate_automation_savings, keeping it from a 5.

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 phrase "from existing steps" and "No actions are executed" imply the situation (you already have documented manual steps and want a written spec, not an execution), but there is no explicit when-to-use or when-not-to-use statement and no mention of the sibling tools. Guidance is inferable rather than stated.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources