Skip to main content
Glama

ai_modeling_canvas_asset_get

Read-only

Inspect a single Canvas result asset by asset ID to review its details and validate generated output.

Instructions

Inspect one Canvas result asset.

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": {
      "assetId": "<assetId>"
    },
    "name": "ai_modeling_canvas_asset_get"
  }
}

Input Schema

NameRequiredDescriptionDefault
assetIdYes

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 by structured data. The description adds nothing beyond that: it does not say what an "inspect" returns, whether the asset must belong to the current session/canvas, or how a missing asset is reported.

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?

A single short sentence with no filler and the key qualifier ("one") up front. It is efficient, though the terseness comes at the cost of information rather than being a model of economical structure.

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?

For a one-parameter read tool with annotations and no output schema, the description could still say what "inspect" yields and what the asset ID must be. As written, an agent knows the shape of the call but not what it gets back or how to obtain a valid ID.

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?

The single assetId parameter has 0% schema description coverage; only a regex pattern and length bounds are supplied. The description does not explain what the ID refers to, where an agent obtains one, or what form ('Canvas result asset' ID vs. a run/turn ID) is expected, so it fails to compensate for the coverage gap.

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?

"Inspect one Canvas result asset" gives a verb and a resource, and the singular "one" plus "asset" signals a per-asset lookup rather than the batch/select siblings. However, "inspect" is vague about what is actually returned — metadata, reference, or content — and it does not explicitly distinguish itself from ai_modeling_canvas_asset_select or ai_modeling_asset_download.

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 any alternative tool. An agent must infer from the name alone that this is the lookup to use when it already holds an asset ID.

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