Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

projects_create

Create a private Ultralytics workspace project by specifying a display name and URL slug, with optional owner, visibility, or description settings to organize your assets.

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. Changed1 schema field changedv0.1.15
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed2 schema fields changedv0.1.13
    • addedInput schema / properties / description / description
      Added value: +"Project description."
    • addedInput schema / properties / name / description
      Added value: +"Display name."
  3. 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"
+]
  4. First observedv0.1.0

TDQS

A3.6/5.0
Behavior4/5

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

Annotations cover the safety profile (not read-only, not idempotent, not destructive), so the bar is lower, but the description adds real value by disclosing that this tool defaults to private visibility while the platform itself defaults to public when visibility is omitted — a non-obvious divergence an agent must know. It stops short of mentioning duplicate-slug errors, auth requirements, or whether the created project is returned.

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, zero waste: purpose first, then the one caveat that changes agent behavior. Perfectly front-loaded.

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

Completeness4/5

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

For a fully documented create tool with annotations covering the mutation profile and no output schema to explain, the description covers what is needed. The remaining gap is failure/ownership edge cases (slug uniqueness, owner defaults), which are secondary.

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 description coverage is 100%, so all five parameters are already documented, including the private/public default for visibility. The description reinforces the visibility default but adds no syntax, constraint, or meaning beyond what the schema states; baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Create a project') scoped to the Ultralytics workspace, which is unambiguous. It does not explicitly name or contrast with the sibling read/delete tools (projects_get, projects_list, projects_delete), but the verb makes the distinction self-evident.

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?

There is no statement of when to use this tool versus alternatives, no prerequisite conditions (e.g., workspace permissions), and no guidance on how it relates to projects_get/projects_list. The only contextual note concerns visibility defaults, which is behavioral rather than usage routing.

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