Simba MCP Server

Official

Overview Schema Source Related Servers Discussions Admin

Create Project

create_project

Create a named project to organize model folders, optionally share it with a team, and receive its ID for saving models.

Instructions

Create a named project (model folder) to file models into.

Names are sanitized the same way model names are (non-empty after HTML sanitization).

Args: name: Display name for the new project. team_id: Optional team to share the project with; must be a team you belong to (403 otherwise, 404 for an unknown team).

Returns the created project (201) including its id — pass that to save_model(project_id=...).

Input Schema

TableJSON Schema

Name	Required	Description	Default
`name`	Yes
`team_id`	No

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedv0.5.0Sep 20, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "title": "create_projectDictOutput",
+  "type": "object"
+}

First observedv0.3.2Aug 28, 2026

TDQS

A4.8/5.0

Behavior5/5

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

The description adds substantial behavior beyond annotations: name sanitization rules, team membership requirements with distinct 403/404 errors, and the 201 response including the created project id. Annotations already indicate a mutating, non-idempotent operation, and the description is consistent with them.

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 concise, front-loaded with the core purpose, and organized into clear sections: purpose, sanitization note, Args, and Returns. Every sentence adds distinct value with no repetition of schema or annotation information.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a two-parameter creation tool with an output schema present, the description covers the essential behavior: display name, sanitation, team-sharing constraints, return status, and how the result connects to save_model. No critical calling information is missing.

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

Parameters5/5

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

Schema description coverage is 0%, but the description fully compensates by explaining both parameters: 'name' as a display name and 'team_id' as optional sharing with an owned team, including error semantics. This adds real meaning beyond the bare schema types.

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 and resource: 'Create a named project (model folder) to file models into.' This clearly distinguishes create_project from sibling tools like create_model and create_recipe_draft by establishing that a project is a container for models.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It gives clear usage context: projects are for filing models into, and the returned id is meant to be passed to save_model(project_id=...). It does not explicitly name alternatives or when-not-to-use conditions, but the workflow hint is strong enough to guide appropriate invocation.

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

Deploy Server