Skip to main content
Glama

ai_modeling_canvas_preview_share

Read-only

Preview which Canvas assets in a project can be shared before publishing or sending them.

Instructions

Preview which Canvas content can be shared.

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>"
    },
    "name": "ai_modeling_canvas_preview_share"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.4

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that the operation previews shareable Canvas content, but it does not explain permissions, return behavior, or whether the preview reflects current sharing configuration.

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?

The description is a single, front-loaded sentence with no redundant wording. Its terseness is efficient, though it borders on under-specification rather than being maximally helpful.

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 simple read-only preview tool, the conceptual return is implied: which Canvas content can be shared. However, with no output schema and no parameter documentation, the description leaves the required projectId and the shape of the preview result under-explained.

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 sole required parameter, projectId, has 0% schema description coverage, and the description never mentions it. The agent can infer that a project context is needed, but the definition adds no meaning about what the projectId identifies or how it affects the preview.

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?

The description states a specific verb and resource: "Preview" plus "Canvas content" that can be shared. It is clear what the tool does, though it does not explicitly distinguish itself from sharing-related siblings such as ai_modeling_share_image or ai_modeling_canvas_get_shared.

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?

The word "Preview" implies checking shareability before actually sharing, but the description gives no explicit when-to-use guidance, prerequisites, or comparison with alternatives. It does not tell the agent when this preview should be preferred over related sharing or access tools.

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