Skip to main content
Glama
Sign In
@vertracloud/mcp

@vertracloud/mcp

Official
by vertracloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

set_blob_visibility

DestructiveIdempotent

Changes a Blob Storage file between public and private. Public files get a permanent URL; private ones need a temporary link. (scope: blob:write)

Instructions

Changes a Blob Storage file between public and private. Public files get a permanent URL; private ones need a temporary link. (scope: blob:write)

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": {
      "id": "<id>",
      "visibility": "<visibility>"
    },
    "name": "set_blob_visibility"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesBlob object ID
visibilityYes
workspace_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.3.0
    • addedInput schema / properties / id / minLength
      Added value: +1
  2. Addedv0.2.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare mutation, destructiveness, idempotency, and open-world behavior. The description adds useful behavioral context beyond annotations: public files get a permanent URL, private files require a temporary link, and the required scope is blob:write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two tightly written sentences with the core action front-loaded. The scope note is compact and every sentence contributes useful information.

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?

The definition covers the main action and access implications, and annotations carry the safety profile. However, with no output schema and incomplete parameter documentation, it leaves gaps around workspace_id and whether the tool returns the public/temporary URL.

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 only 33%, and the description does not compensate by explaining the parameters. It implies the visibility enum values but does not document id or workspace_id semantics, which matters because workspace_id is an optional scoping parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a specific verb and resource: changing a Blob Storage file between public and private. It clearly distinguishes the operation from sibling blob tools like upload_blob, delete_blob_object, get_blob_object, and blob_download_url.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives clear context for when to use the tool: toggling a blob between public and private, with implications for URL access. It does not explicitly name alternatives or when-not to use it, so it falls short of the top score.

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