Skip to main content
Glama
Sign In
errorbar

errorbar

by omnia-v
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

list aliases

list_aliases
Read-onlyIdempotent

Retrieve workspace model aliases to inspect stable names, current target models, canary routing, quality-gate settings, evidence policy, and the eval run authorizing each routing.

Instructions

List this workspace's model aliases (stable names your code calls) with their current target, canary split, quality-gate config, evidence policy and the eval run that authorized the current routing. GET /v1/aliases (API-key scope: read). Returns: { object: "list", data: [{ id, name, target_model, canary_model, canary_percent, description, gate_criterion_id, gate_mode ("recommend"|"auto"), gate_min_samples, gate_rollback_threshold, gate_window_hours, gate_verdict ({decision, reason, canary, incumbent, acted}|null), gate_verdict_at, model_version_id, require_evidence, last_evidence_run_id, created_at, updated_at }] } Notes: Sorted by name ascending. last_evidence_run_id is null when the routing predates the evidence policy or went through as an audited override.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_aliases"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.5.1

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already mark it read-only/idempotent, and the description adds the endpoint, API-key scope, sorting behavior (name ascending), and nuanced null semantics for last_evidence_run_id. It also exposes the full response envelope so the agent knows exactly what to expect beyond the safety profile.

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 structured with a concise purpose sentence, endpoint/auth note, explicit return shape, and a focused note about null behavior. Each part provides actionable information without duplication, so it is appropriately sized for a rich read-only list operation.

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?

With no output schema provided, the description compensates with a full field list, enum values, null semantics, sort order, and authentication scope. This is complete enough for an agent to invoke the tool and interpret the result correctly in a workspace context.

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?

The tool has zero parameters, and the schema coverage is 100% (empty schema). The baseline of 4 applies because there are no parameter semantics to clarify; the description does not need to compensate for undocumented parameters.

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 names a specific verb ('List'), resource ('this workspace's model aliases'), and enumerates exactly what is included (target, canary split, quality-gate config, evidence policy, authoring eval run). This clearly distinguishes the read-only listing from mutation siblings like upsert_alias and delete_alias.

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 context for when the tool is relevant: inspecting the stable names your code calls and their current routing details. It does not explicitly name alternatives or state when not to use it, but the read-only 'GET /v1/aliases' phrasing plus sibling names make the usage context unambiguous.

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