Skip to main content
Glama

List Ducks

list_ducks
Read-only

Lists all available LLM providers and their status, optionally running health checks to verify each provider is reachable before use.

Instructions

List all available LLM providers (ducks) and their status

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_ducks"
  }
}

Input Schema

NameRequiredDescriptionDefault
check_healthNoPerform health check on all providers

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.20.14
    • removedInput schema / additionalProperties
      Removed value: -false
  2. Addedv1.19.6
  3. Removedv1.19.5
  4. Changed2 schema fields changedv1.2.3
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • addedInput schema / additionalProperties
      Added value: +false
  5. First observedv1.0.0

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds that each provider's "status" is returned, but it does not warn that check_health may trigger slow network probing or explain what a provider status value looks like, which matters for a single-flag tool.

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?

One short sentence, front-loaded with the verb and the resource, with the parenthetical clarifying the ambiguous term "ducks." Nothing is redundant.

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?

For a zero-required-parameter read-only listing with full schema coverage and no output schema, the description is minimally sufficient. It still omits how results differ from list_models and what "status" entails, gaps an agent would notice when choosing between the two listing tools.

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 the single boolean is already documented as "Perform health check on all providers." The description's phrase "and their status" lightly reinforces this but adds no cost, latency, or default-behavior detail beyond the schema.

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?

The description uses a clear verb+resource ("List all available LLM providers") and disambiguates the domain jargon by equating "ducks" with LLM providers. It does not, however, distinguish this from the sibling list_models, leaving an agent to guess whether providers and models are the same listing.

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 explicit when-to-use guidance, no exclusions, and no mention of alternatives such as list_models or compare_ducks. The agent must infer that this is the discovery/entry-point call before invoking ask_duck or chat_with_duck.

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