Skip to main content
Glama

ai_modeling_project_visibility

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

Instructions

Set your 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": {
      "project_id": "<project_id>",
      "visibility": "<visibility>"
    },
    "name": "ai_modeling_project_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
project_idYes
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 and openWorldHint=true, so the bar is lower, but the description adds nothing beyond that: it does not say who gains or loses access, whether existing share links break, or whether the change is immediately effective. For a mutating permission operation, that omission is material.

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 short sentence with no filler, but it is under-specified rather than efficiently concise. There is nothing to front-load because nothing specific is stated.

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?

This is an external-facing, permission-changing mutation with no output schema and no documented parameters; the description does not cover effect, permissions, or return behavior. It is far too thin for the tool's risk profile.

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 must carry the parameter meaning, and it does not — in particular the distinction between "public", "private", and "shareable" is never explained, nor is the accepted format of project_id. Two required parameters with no added semantics is a real 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?

The sentence names a verb ("Set") and resource ("project visibility"), so the intent is inferable, but it largely restates the tool name and says nothing about scope or effect. It only weakly distinguishes itself from the sibling ai_modeling_canvas_visibility beyond the word "project".

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 mention of prerequisites such as ownership or admin rights, and no routing to alternatives like ai_modeling_canvas_visibility. The agent must guess whether this is the right tool for the object it holds.

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