Skip to main content
Glama
amanharshx

ultralytics-mcp

by amanharshx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

deployment_metrics

Read-only

Retrieve metrics for a specific deployment by owner/slug or bare slug, with configurable time range and optional compact sparkline for 24-hour request stats.

Instructions

Read metrics for one deployment by owner/deployment or a bare slug (owner defaults to the account owner). The response is one of two shapes selected by sparkline: the default shape carries timeRange (a {start, end} object)/summary/timeSeries, sparkline=true carries requests24h (an array of per-hour points, not a total)/totalRequests/errorRate/avgLatencyMs. The two are never merged; which shape came back is returned as-is. range (e.g. 1h, 24h, 7d; default 24h) is passed through to the server unvalidated.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
rangeNoTime range, passed through unvalidated (e.g. 1h, 24h, 7d; default 24h).
sparklineNoWhen true, selects the compact sparkline shape (requests24h, totalRequests, errorRate, avgLatencyMs) instead of the detailed shape.
deploymentYesDeployment ref by owner/deployment or a bare slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.1.15
    • addedInput schema / additionalProperties
      Added value: +false
  2. Changed1 schema field changedv0.1.13
    • changedInput schema / properties / range / description
      Previous value: -"Time range, passed through unvalidated (one of 1h, 6h, 24h, 7d, 30d; default 24h)."New value: +"Time range, passed through unvalidated (e.g. 1h, 24h, 7d; default 24h)."
  3. Addedv0.1.12

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare readOnly/non-destructive, and the description goes well beyond them: it discloses the two mutually exclusive response shapes, that they are never merged, which fields each carries, that requests24h is per-hour points not a total, and that range is passed through to the server unvalidated. That is exactly the behavioral context an agent needs.

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

Conciseness4/5

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

A single dense paragraph that is front-loaded with the invocation form and then the response shapes. Nearly every clause earns its place, though the response-shape enumeration is slightly heavy for a definition with no output schema.

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?

No output schema exists, so the description carries return-value detail itself, and it does so completely across both shapes. Deployment ref resolution, range default, and validation behavior are all covered, leaving nothing an agent needs missing.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: the owner component of a bare slug defaults to the account owner (not stated in the schema) and reiterates that range is unvalidated and default 24h. The sparkline explanation mostly mirrors the schema but frames it in terms of return shape selection.

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?

States a specific verb and resource ('Read metrics for one deployment') plus the accepted ref forms. It is distinguishable from siblings like deployment_health, deployment_logs, and model_metrics without opening any schema.

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 description explains how to invoke the tool and what each mode returns, but never says when to prefer it over deployment_health, deployment_logs, or model_metrics, and gives no explicit exclusions. Usage is implied by the resource rather than stated.

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