List model deployments in your Ultralytics workspace to review active endpoints and manage deployed models.
List model deployments in your Ultralytics workspace.
| Name | Required | Description | Default |
|---|---|---|---|
| owner | No | Workspace owner; defaults to the account owner. |
Changes observed during successful MCP inspections.
v0.1.12Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true and destructiveHint=false, covering the main safety profile. The description adds only the workspace scope and does not disclose additional behavior such as pagination, limits, or authentication requirements.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no filler. It states the action and scope efficiently, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a simple read-only list operation with one optional documented parameter and annotations carrying the safety profile, the description is mostly complete. It lacks explicit output details or pagination behavior, but nothing critical is missing for invoking the tool correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, and the single optional owner parameter is well documented in the schema with its default behavior. The description adds no extra meaning to the parameter, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description uses a specific verb ('List') and resource ('model deployments'), and scopes it to 'your Ultralytics workspace.' This clearly distinguishes it from related sibling tools like deployment_get, deployment_health, and models_list.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is given about when to use this tool instead of alternatives such as deployment_get or deployment_logs. There is no mention of exclusions, prerequisites, or when a different tool would be more appropriate.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.