Skip to main content
Glama

ai_modeling_canvas_input_assets

Read-only

Inspect imported Canvas input assets and check their readiness before modeling. Provide project and asset IDs to confirm availability and processing status.

Instructions

Inspect imported Canvas input assets and their readiness.

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": {
      "projectId": "<projectId>",
      "assetIds": "<assetIds>"
    },
    "name": "ai_modeling_canvas_input_assets"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdsYes
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

C2.4/5.0
Behavior2/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 the safety profile is covered without the description. The only added behavior is that the assets are "imported" and have a "readiness" state, without saying what readiness means, whether results are per-asset, or how failures are reported for unknown asset IDs.

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?

One front-loaded sentence with no wasted words, which is good structurally. The terseness, however, is under-specification rather than disciplined concision, since key concepts like readiness are left opaque.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema and 0% parameter documentation, the description needed to explain what an inspection returns about readiness and how assetIds are matched. Neither is covered, leaving the tool callable but its results unpredictable.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for two required parameters, so the description carries the full explanatory burden and adds nothing about projectId scoping or that assetIds is a batch of 1-100 identifiers. An agent gets no meaning beyond the field names and JSON Schema constraints.

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 names a verb ("Inspect") and a resource ("imported Canvas input assets"), which is better than a tautology, but "inspect" is broad and "readiness" is never defined. It also gives no signal to distinguish it from near-neighbors such as ai_modeling_canvas_asset_get or ai_modeling_canvas_node_assets.

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 prerequisites, and no mention of alternatives for retrieving Canvas asset information. The agent must infer the trigger condition entirely from the tool name.

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