Skip to main content
Glama

Read Canvas planning knowledge and live model facts

aimixer_canvas_knowledge
Read-onlyIdempotent

Call first without topics: the response carries the topic index with routes from the user's goal to topics and sections. Read bounded Canvas planning policy, including the near-square grid rule for groups/frames (ceil(sqrt(N)) columns, row-major, no overlap), paged model cards with practical advice, and a paged live catalog projection of current variants, modes, inputs and public parameters. Cards guide workflow; only live descriptors define availability/parameters. Prices are excluded and must come from estimate/validate.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
offsetNo
topicsNo
model_keyNo
card_limitNo
card_offsetNo
catalog_subNo
detail_limitNo
detail_offsetNo

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.6/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the bar is lower, and the description does add real context: the first call returns a topic index with routes, results are paged, and prices are deliberately excluded. It still omits practical behavior such as what happens when topics exceed the maxItems limit of 4 or how the three separate paging cursors interact.

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

Conciseness4/5

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

Front-loads the single most important instruction ('Call first without topics') and then layers policy, content types, and the authority/price caveats. Sentences are dense but each carries information; the parenthetical grid-rule formula is somewhat heavy for a description but is genuine content.

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 description covers the tool's dual nature (static knowledge vs live facts), paging, and the price exclusion. The remaining gap is parameter-level coverage for the four paging/catalog arguments, which leaves an agent guessing on a 10-parameter 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?

With 0% schema description coverage across 10 parameters, the description must carry the load, and it only partially does: it explains the semantics of topics (omit to get the index), mentions paging, and implies kind/model_key via 'variants, modes, inputs and public parameters.' It never distinguishes limit from card_limit from detail_limit, nor explains catalog_sub or the 4-topic cap.

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?

Specific verb+resource: it reads Canvas planning knowledge plus a live catalog projection of variants, modes, inputs and parameters. It also distinguishes itself from model cards by stating cards are advice while 'only live descriptors define availability/parameters,' though it never names which sibling serves cards or prices.

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?

Gives explicit entry guidance — 'Call first without topics' to get the topic index and routes — plus precedence rules (cards guide workflow, live descriptors are authoritative) and a clear exclusion (prices must come from estimate/validate). It stops short of naming the specific sibling tools for those alternate paths.

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