Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

projects_create

Create an Ultralytics workspace project, defaulting to private visibility. Set the display name, URL slug, owner, description, and choose public or private access.

Instructions

Create a project in your Ultralytics workspace. Defaults to private visibility (the platform defaults to public when visibility is omitted).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesDisplay name.
ownerNoWorkspace owner; defaults to the account owner.
projectYesURL slug for the new project (distinct from the display name given by name).
visibilityNoVisibility "private" (default) or "public".
descriptionNoProject description.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.13
    • addedInput schema / properties / description / description
      Added value: +"Project description."
    • addedInput schema / properties / name / description
      Added value: +"Display name."
  2. Changed5 schema fields changedv0.1.12
    • addedInput schema / properties / owner
      Added value: +{
+  "description": "Workspace owner; defaults to the account owner.",
+  "type": "string"
+}
    • addedInput schema / properties / project
      Added value: +{
+  "description": "URL slug for the new project (distinct from the display name given by name).",
+  "type": "string"
+}
    • removedInput schema / properties / slug
      Removed value: -{
-  "type": "string"
-}
    • addedInput schema / properties / visibility
      Added value: +{
+  "description": "Visibility \"private\" (default) or \"public\".",
+  "type": "string"
+}
    • changedInput schema / required
      Previous value: -[
-  "name"
-]New value: +[
+  "name",
+  "project"
+]
  3. First observedv0.1.0

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover the mutation profile (readOnlyHint=false), and the description adds a genuinely useful behavioral nuance: the tool defaults to private visibility while the platform would otherwise default to public when the field is omitted. This goes beyond structured fields and helps the agent avoid an unwanted public project.

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?

Two sentences with no filler: the primary action is front-loaded, and the parenthetical about platform defaults earns its place because it prevents a costly mistake. Nothing unnecessary is included.

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?

All 5 parameters are documented in the schema and annotations cover safety semantics, making basic invocation complete. However, the description omits uniqueness constraints, error behavior, or what happens if the project slug already exists—minor but real gaps for a create operation with no output schema.

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?

Input schema coverage is 100%, and every parameter has a description. The description adds context for visibility by explaining the default behavior, but this largely mirrors the schema's 'private (default)' note. With full schema coverage, a baseline of 3 is appropriate.

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 a specific verb and resource: 'Create a project in your Ultralytics workspace.' It is unmistakably a creation operation, clearly distinct from sibling tools like projects_list, projects_get, and projects_delete without needing to inspect their schemas.

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 intended use is implied by the action 'Create a project,' but the description offers no explicit when-to-use guidance or alternatives. It does not tell the agent when to prefer this over related project tools or mention exclusions, so usage context is only implicit.

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

Deploy Server

Other Tools