Skip to main content
Glama

Оформление отчётов аккаунта

get_workspace_report_appearance
Read-onlyIdempotent

Возвращает оформление отчётов уровня аккаунта: общую палитру, библиотеку сохранённых наборов, значения по умолчанию и допустимые значения каждого поля. Опросы с results_appearance_use_shared = true рисуют отчёты общей палитрой; свои цвета опроса при этом сохраняются и вернутся, если флаг выключить.

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": "get_workspace_report_appearance"
  }
}

Input Schema

NameRequiredDescriptionDefault
workspace_idYesID воркспейса (из workspace://list).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, closed-world, and non-destructive, so safety is covered. The description adds genuinely non-obvious behavior beyond them: the inheritance rule for quizzes with results_appearance_use_shared = true and the guarantee that per-quiz colors survive and reappear when the flag is turned off. That is real semantic context an agent cannot get from annotations.

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?

Two sentences, front-loaded with the resource and its contents. The second sentence on inheritance is dense but arguably secondary; it earns its place by explaining interpretation of results, though it could be separated or trimmed slightly.

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?

With no output schema, the description carries the burden of describing return contents, and it does so by listing palette, preset library, defaults, and allowed values per field. Combined with the inheritance note, an agent can call this correctly, though it lacks guidance on how the returned presets relate to the preset-management siblings.

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?

Only one parameter, documented at 100% schema coverage including its source (workspace://list). The description adds no meaning beyond the schema for workspace_id, so the 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 names a specific resource (account-level report appearance) and enumerates what it returns: shared palette, saved preset library, defaults, and allowed values per field. It does not explicitly name the sibling write tool (update_workspace_report_palette) or preset tools it complements, so differentiation is implied through the 'returns' framing rather than stated.

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 only implied: an agent can infer this is the read-side counterpart to the palette/preset mutation tools, but the description never says when to call it or what to do instead for other purposes. No exclusions or prerequisites (e.g., that workspace_id must come from workspace://list) are stated in the description itself.

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