SemaphoreUI MCP Server

Overview Schema Source Related Servers Discussions Admin

create_project

Create a new SemaphoreUI project for managing Ansible automation, with optional alerting, parallel task limits, project type, and demo resources.

Instructions

Create a new project.

Args: name: Project name alert: Enable alerts (default: False) alert_chat: Chat channel for alerts (optional) max_parallel_tasks: Maximum parallel tasks, 0 = unlimited (default: 0) project_type: Project type (optional) demo: Create demo resources (default: False)

Returns: Created project details

Input Schema

TableJSON Schema

Name	Required	Description	Default
`demo`	No
`name`	Yes
`alert`	No
`alert_chat`	No
`project_type`	No
`max_parallel_tasks`	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.5/5.0

Behavior2/5

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

No annotations are provided, and the description only says 'Create a new project.' No disclosure of side effects, authorization needs, or behavior on duplicate names or failures.

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

Conciseness5/5

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

The description is a well-structured docstring with Args and Returns sections. It is concise, front-loading the purpose, and uses minimal words to cover all parameters.

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?

The description mentions that the tool returns 'Created project details', but does not detail the structure or include edge-case handling. Given an output schema exists, the description is adequate but not comprehensive.

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 functional meaning to each parameter, such as 'Enable alerts (default: False)' and 'Maximum parallel tasks, 0 = unlimited'. This significantly compensates for the schema's lack of descriptions.

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 states 'Create a new project' with a specific verb and resource. It clearly distinguishes from sibling tools like 'update_project' and 'delete_project'.

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 on when to use this tool versus alternatives (e.g., 'clone_project'). The description does not mention prerequisites, common use cases, or avoid scenarios.

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

Deploy Server