Skip to main content
Glama

Canvas Continuity Capabilities

aimixer_canvas_continuity_capabilities
Read-onlyIdempotent

Offline provider-neutral Canvas continuity library. Pass model_key for one exact video model; omit it to list every current Canvas model whose public descriptor accepts a first frame. The list updates from the live Canvas catalog, is not provider verification and is NEVER a paid approval.

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": "aimixer_canvas_continuity_capabilities"
  }
}

Input Schema

NameRequiredDescriptionDefault
model_keyNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "additionalProperties": true,
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Beyond the read-only and idempotent annotations, it discloses provider neutrality, descriptor-based rather than provider-verified results, a live catalog source, and the absence of paid approval. However, "Offline" alongside "updates from the live Canvas catalog" leaves the refresh and data-source behavior somewhat ambiguous.

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?

Three short sentences cover the purpose, both invocation modes, and result limitations without filler. Every sentence earns its place, and the operational guidance is easy to scan.

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?

For a one-parameter read-only tool with an output schema, this is nearly sufficient to select and invoke it correctly. Sibling routing, valid-key discovery guidance, and clarification of the offline/live-catalog wording would make it more complete.

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?

With 0% schema description coverage, the description usefully explains that model_key selects one exact video model and that omitting it produces the full eligible-model list. It does not say where to obtain valid keys or how unknown keys are handled.

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 identifies a Canvas continuity-capability lookup and gives a precise listing criterion: models whose public descriptor accepts a first frame. It does not explicitly differentiate this tool from the general capabilities, model-discovery, or model-description siblings, so it stops short of a 5.

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?

Passing model_key versus omitting it provides concrete mode-selection guidance, while "not provider verification" and "NEVER a paid approval" establish important when-not limits. It does not route the agent to another tool for verification, approval, or discovering a valid key.

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