Skip to main content
Glama

List capabilities

list_capabilities
Read-only

List what Windpaint can do. For each capability: description, output kind, whether a prompt is required and what it means, the input slots (name, accepted asset kinds, min/max count), and the models that implement it with available, licence, resolutions, qualities, durations, max_outputs, output_formats and the current credit price per tier. A capability with no available model cannot be run yet. Call this first. By default only models you can run now are listed in full; the rest are summed up in unavailable_models (model, status and why it can't run). Pass capability (e.g. "video.generate") to get just one, and available_only=false for the full catalog, including every model that can't run yet.

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

Input Schema

NameRequiredDescriptionDefault
capabilityNo
available_onlyNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint, so the description carries most of the burden and does add real behavior: by default unavailable models are collapsed into `unavailable_models` with status and reason, a capability with no available model cannot be run, and per-tier credit prices are returned. The main missing piece is whether discovery is cached or whether the catalog changes between calls, but the default-vs-full output difference is well disclosed.

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

Conciseness3/5

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

Front-loaded and purposeful, but the long mid-sentence enumeration of return fields (licence, resolutions, qualities, durations, max_outputs, output_formats, credit price) is dense and partly redundant since an output schema exists. Readable, yet it spends words on return-shape detail that structured data already covers.

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?

Given only two optional params and a rich output schema, the description is nearly complete: it explains defaults, the unavailable-model summarization, pricing, and the read-only discovery role. Redundancy in re-describing return fields is wasted but not harmful, and the lack of valid `capability` values is the only material omission.

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 description coverage is 0%, so the description must compensate and largely does: `capability` is explained as a filter with the example "video.generate", and `available_only` is explained with its default effect (only runnable models listed in full, rest summarized). The one gap is that no enumeration of valid capability values is given, so an agent must guess the identifier namespace beyond the single example.

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+resource (list what Windpaint can do) and immediately enumerates what a capability record contains: description, output kind, prompt requirement, input slots, implementing models with availability, licence, resolutions, and credit price per tier. This is clearly a catalog/discovery tool, readily distinguishable from siblings like list_assets, list_loras or list_workflows that enumerate concrete user objects.

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?

"Call this first" is explicit ordering guidance, and the description explains how to narrow scope with `capability` for a single entry or `available_only=false` for the full catalog. There is no explicit "when not to use" or named alternative tool, but the entry-point framing makes the intended usage unambiguous.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources