Skip to main content
Glama

Палитра отчётов аккаунта

update_workspace_report_palette
Destructive

Задаёт общую палитру отчётов аккаунта. Все опросы с results_appearance_use_shared = true сразу начинают рисовать отчёты ею, свои цвета опросов при этом не трогаются. Требуется право account_quiz_settings.

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

Input Schema

NameRequiredDescriptionDefault
settingsYesОбъект оформления. Неизвестные значения приводятся к стандартным, а не отклоняют вызов.
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already flag a destructive, non-idempotent mutation, and the description usefully adds blast radius: every shared-appearance survey starts rendering with the new palette immediately, while per-survey colors are left intact. The stated permission requirement is also value beyond the structured fields. It does not describe the response or whether other appearance fields are reset.

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?

Three sentences, front-loaded with the action, then the propagation effect, then the permission. No filler, and each sentence contributes a distinct fact.

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 destructive mutation with a nested settings object and no output schema, the description covers scope, propagation, non-impact on survey-level colors, and authorization. Only the result/return behavior is unaddressed, which is minor given the lack of an output schema.

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%, and the nested settings object is fully documented with enum meanings and fallback behavior, so the schema carries the parameter burden. The description only clarifies the semantic consequence of the shared flag, not the parameters themselves; baseline 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 opens with a specific verb and resource: setting the shared report palette of the account. Its scope ('общую палитру отчётов аккаунта') is distinguishable from theming/branding siblings, though no sibling is named explicitly.

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?

It states the precondition (permission account_quiz_settings) and the effect condition (surveys with results_appearance_use_shared = true), which implies when the tool applies. However, it never contrasts this with update_theme or update_workspace_branding, so the agent must infer when to prefer this tool.

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