Skip to main content
Glama

ai_modeling_canvas_template_asset_get

Read-only

Retrieve a model asset embedded in a Canvas template using its template and asset IDs. Use it to inspect or reuse template model assets, though image assets may not be available.

Instructions

Read a model asset embedded in a Canvas template. Image assets may be unavailable through this endpoint.

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

Input Schema

NameRequiredDescriptionDefault
assetIdYes
templateIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds one genuinely non-structured fact — that image assets may fail to be returned here — but says nothing about permissions, error behavior when unavailable, or what the response contains.

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?

Two short sentences, zero padding, and the core action is front-loaded. The second sentence is slightly vague ("may be unavailable" leaves the agent unsure whether it is an error or an empty result).

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 retrieval tool with no output schema and zero documented parameters, the description should say what is returned (metadata, reference, or binary content) and how the image-unavailability case manifests. Neither gap is addressed, leaving the agent unable to interpret the result.

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%, so the description carries the full burden for templateId and assetId, yet it only obliquely alludes to "a Canvas template" and "asset." It adds no meaning about ID formats, provenance, or whether the assetId must belong to the given template.

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?

"Read a model asset embedded in a Canvas template" gives a specific verb (read) and a specific resource (template-embedded asset), which distinguishes it from the standalone asset-fetch sibling. It stops short of naming the sibling it differs from, so an agent must infer the distinction from the phrase "embedded in a Canvas template."

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 only implied: the tool applies when the asset lives inside a template rather than a canvas. The clause "Image assets may be unavailable through this endpoint" is a partial when-not signal, but no alternative tool is named for that case, so the agent gets a warning without a route.

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