semaphore-mcp-server

template_create

Create a job template for automation workflows by specifying project, playbook, inventory, and repository.

Instructions

Create a new template (job template).

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": {
      "project_id": "<project_id>",
      "name": "<name>",
      "playbook": "<playbook>",
      "inventory_id": "<inventory_id>",
      "repository_id": "<repository_id>"
    },
    "name": "template_create"
  }
}

Input Schema

Name	Required	Description
`project_id`	Yes	The ID of the project.
`name`	Yes	Template name.
`playbook`	Yes	Playbook filename to run.
`inventory_id`	Yes	ID of the inventory to use.
`repository_id`	Yes	ID of the repository containing the playbook.
`environment_id`	No	ID of the environment (optional).
`description`	No	Template description (optional).
`arguments`	No	Extra CLI arguments as JSON array string (optional).
`allow_override_args_in_task`	No	Allow overriding arguments per task.
`suppress_success_alerts`	No	Suppress alerts on success.

Output Schema

Name	Required	Description	Default
`result`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1Jun 17, 2026

TDQS

C2.8/5.0

Behavior1/5

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

With no annotations, the description must disclose behavioral traits, but it only states the action. It omits side effects, idempotency, duplicate handling, or any safety implications.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

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

The description is a single sentence, which is concise, but it is under-specified for a tool with 10 parameters. It could be more informative without being verbose.

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 the tool has many parameters and no annotations, the description lacks context about its role in the system, common usage patterns, or output structure (though output schema exists). Incomplete for agent understanding.

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 100%, so the schema already documents all parameters. The description adds no additional parameter information, meeting the baseline of 3.

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 specific verb ('Create') and resource ('template'), and clarifies it's a job template, distinguishing it from sibling tools like template_get, template_list, template_delete.

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 is provided on when to use this tool versus alternatives (e.g., environment_create, inventory_create). There are no prerequisites or contextual usage hints.

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