Skip to main content
Glama

Canvas Validate Workflow

aimixer_canvas_validate_workflow
Read-onlyIdempotent

Read-only Canvas graph validation: dependency order, missing models/media and continuity blockers. No billing, no prepare_execution, no provider requests. An unknown cost is NOT a quote.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project_id": "<project_id>"
    },
    "name": "aimixer_canvas_validate_workflow"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes

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

A3.8/5.0
Behavior4/5

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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world behavior, so the description clears a lower bar. It still adds genuine value beyond them: explicit no-billing and no-provider-request guarantees, and the caveat that an unknown cost is not a quote, which prevents an agent from misreading validation output as pricing.

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, zero filler, with the read-only scope front-loaded and the negative guarantees following. Every clause carries information an agent would otherwise have to guess.

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?

An output schema exists, so return values need not be described, and the annotations cover the safety profile fully. The description supplies the remaining scope and side-effect boundaries; only the failure semantics (does an invalid graph raise or return a findings list) are left to the output schema.

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?

The schema has 0% description coverage for project_id, but the single required parameter is self-explanatory by name and the description adds nothing about its format or scope. With one obvious identifier parameter, this is adequate rather than deficient, but no extra meaning is contributed.

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 names a specific verb and resource ('Read-only Canvas graph validation') and enumerates the checks performed: dependency order, missing models/media, and continuity blockers. It also distinguishes itself negatively from prepare_execution, though it does not contrast with closer read-side siblings such as preview or inspect_layout.

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?

Usage is implied rather than stated: by declaring 'no billing, no prepare_execution, no provider requests,' it signals this is the safe pre-flight check before execution, but it never says 'call this before prepare_execution' or when to prefer it over preview/inspect tools. The reader must infer the workflow position.

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