SemaphoreUI MCP Server

Overview Schema Source Related Servers Discussions Admin

create_template

Create a reusable Ansible template to standardize automation runs by defining project, playbook, inventory, repository, and environment parameters.

Instructions

Create a new template.

Args: project_id: ID of the project name: Template name playbook: Playbook file path (e.g., "playbook.yml") inventory_id: Inventory ID repository_id: Repository ID environment_id: Environment ID description: Template description (optional) arguments: Extra arguments as JSON string (optional) allow_override_args_in_task: Allow overriding arguments in task (default: False) suppress_success_alerts: Suppress success alerts (default: False) app: Application type (default: "ansible") git_branch: Git branch to use (optional) survey_vars: Survey variables for prompting (optional) vaults: Vault configurations (optional) template_type: Template type - "", "build", or "deploy" (optional) start_version: Start version (optional) build_template_id: Build template ID for deploy templates (optional) autorun: Enable autorun (default: False) view_id: View ID (optional) task_params: App-specific task parameters (optional). For Ansible templates: - allow_override_limit: Allow task-level --limit override (required for run_task limit) - allow_override_inventory: Allow task-level inventory override - allow_override_tags: Allow task-level --tags override - allow_override_skip_tags: Allow task-level --skip-tags override - limit: Default limit (list of hosts/groups) - tags: Default tags (list) - skip_tags: Default skip tags (list)

Returns: Created template details

Input Schema

TableJSON Schema

Name	Required	Default
`app`	No	ansible
`name`	Yes
`vaults`	No
`autorun`	No
`view_id`	No
`playbook`	Yes
`arguments`	No
`git_branch`	No
`project_id`	Yes
`description`	No
`survey_vars`	No
`task_params`	No
`inventory_id`	Yes
`repository_id`	Yes
`start_version`	No
`template_type`	No
`environment_id`	Yes
`build_template_id`	No
`suppress_success_alerts`	No
`allow_override_args_in_task`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.4Jun 3, 2026

TDQS

A3.6/5.0

Behavior2/5

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

No annotations are provided, so the description carries full burden. It does not disclose side effects, permissions, idempotency, or error behaviors beyond stating 'Creates' and 'Returns created template details.' This is minimal disclosure for a mutation tool.

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?

The description is well-structured with separate Args and Returns sections. It lists numerous parameters clearly but could be slightly more concise by grouping defaults. Overall, it earns its length given the parameter count.

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?

Given the complexity (20 parameters) and existence of an output schema, the description covers parameter purposes fairly well. However, it lacks operational context such as behavior of template_type variants or failure scenarios, leaving some gaps.

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

Parameters4/5

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

With 0% schema coverage, the description adds significant meaning to parameters, e.g., explaining task_params structure for Ansible, default values, and optionality. However, some parameters like vaults and survey_vars lack detailed semantics beyond type.

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 clearly states 'Create a new template,' specifying the exact action and resource. This contrasts with siblings like update_template and delete_template, making it distinct.

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 description implies creation use but does not explicitly state when to use this tool versus alternatives, nor does it provide prerequisites or exclusions. It lacks guidance on conditions for choosing this tool over others.

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

Deploy Server