Skip to main content
Glama

ai_modeling_canvas_visibility

Set a Canvas project's visibility to private, public, or shareable to control who can access and share it.

Instructions

Change Canvas project visibility.

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

Input Schema

NameRequiredDescriptionDefault
projectIdYes
visibilityYes

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=false, destructiveHint=false, and openWorldHint=true, so the safety profile is mostly covered. The description adds nothing beyond that: it does not say whether making a canvas public exposes it to anyone with a link, whether existing shares are affected, or whether the change is reversible — meaningful context for a visibility mutation.

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?

A single short sentence with no wasted words and the action front-loaded, but it is under-specified rather than concise. There is no structure beyond the one clause.

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 two-required-parameter mutation with no output schema and zero schema documentation, the description should explain at least the visibility levels and any side effects. As written it omits both, leaving the agent under-informed before performing an outward-facing change.

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 and fails it. It never explains that projectId identifies the target canvas, and critically never distinguishes VISIBILITY_PRIVATE, VISIBILITY_PUBLIC, and VISIBILITY_SHAREABLE — the enum values whose semantics an agent most needs before making a project publicly accessible.

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 specific verb and resource ('Change Canvas project visibility'), which is clearer than a tautology. However, it does nothing to distinguish this tool from the sibling ai_modeling_project_visibility, nor does it clarify whether 'Canvas project' differs from the 'project' in that sibling.

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 guidance on when this tool should be used versus ai_modeling_project_visibility or ai_modeling_canvas_access, and no stated prerequisites such as ownership or admin permission required to change visibility. The agent is left to infer everything about selection.

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