Skip to main content
Glama

Логотип и копирайт аккаунта

update_workspace_branding
Destructive

Настраивает брендинг рабочего пространства: показ логотипа и копирайта WebAsk. Настройки общие для всех опросов пространства. Скрытие копирайта доступно не на всех тарифах.

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": {
      "workspace_id": "<workspace_id>"
    },
    "name": "update_workspace_branding"
  }
}

Input Schema

NameRequiredDescriptionDefault
logo_showNoПоказывать логотип рабочего пространства в опросах.
workspace_idYesID рабочего пространства. Взять из workspace://list.
show_copyrightNoПоказывать копирайт WebAsk. Скрытие (false) доступно не на всех тарифах.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered structurally. The description adds real context beyond them — the change propagates to every survey in the workspace and the copyright toggle depends on the subscription tier — but it never explains why the call is flagged destructive or whether prior values can be restored.

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?

Three short sentences, front-loaded with the core action and followed by the scope and plan constraints; nothing is filler. The tariff caveat is slightly duplicated in the schema, a minor redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a three-parameter mutation with full schema coverage and no output schema, the description supplies the two pieces of context an agent most needs: workspace-wide blast radius and tier gating. Only the reversibility/restore story is left unaddressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, with all three parameters documented, including the plan restriction on show_copyright. The description's mention of logo and copyright display restates rather than extends the schema, so the baseline of 3 applies.

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 gives a specific verb and resource ('Настраивает брендинг рабочего пространства') and enumerates the two controllable facets (logo display, WebAsk copyright). It does not explicitly differentiate itself from near neighbours such as delete_workspace_logo or update_workspace_report_palette, so it stops short of a 5.

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 implied rather than stated: the agent learns the settings apply workspace-wide and that hiding copyright is plan-gated, which frames when the call is appropriate. There is no explicit when-to-use/when-not guidance and no named alternative for logo removal versus logo visibility.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources