Skip to main content
Glama

ai_modeling_canvas_tools

Read-only

Retrieves the live creative tools available to the Canvas agent so you can identify supported Canvas operations.

Instructions

Read the live creative tools available to the Canvas agent.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so safety and openness are covered by structured data. The word 'live' adds a small behavioral hint that the returned set is dynamic rather than static. Beyond that, the description says nothing about cost, rate, caching, or what 'live' actually entails, so with the lower annotation-driven bar this is a modest add.

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?

A single short sentence with the object of the action front-loaded and no filler whatsoever. There is no redundancy or buried information to trim.

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 no-parameter read with full annotation coverage, most of what an agent needs is present; the annotations handle safety and openness. The gap is that there is no output schema, so the description should have said what is returned -- a list of tool names, definitions, or capabilities -- and it does not. That is the remaining hole for a pure discovery call.

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?

The tool takes zero parameters and the schema has additionalProperties=false, so there is no parameter meaning to explain; the baseline of 4 applies. The description does not need to compensate for any schema gap here.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a clear verb ('Read') and a resource ('the live creative tools available to the Canvas agent'), so the general intent is a discovery/listing operation. However, 'creative tools' is never defined, and it is not obvious how this differs from adjacent-sounding siblings such as ai_modeling_canvas_lab, ai_modeling_canvas_access, or ai_modeling_canvas_get. An agent can guess it enumerates available tools but not precisely what those tools are.

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 when-to-use guidance, no prerequisite, and no named alternative or exclusion. Nothing tells the agent whether this should be called before driving the canvas, when it is stale, or when a sibling such as canvas_get or canvas_lab is the better choice.

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

Deploy Server

Other Tools