Skip to main content
Glama

Новый набор оформления отчёта

create_report_appearance_preset

Сохраняет набор оформления в библиотеку аккаунта, чтобы применять его к другим опросам. Набор — это шаблон: его удаление или правка не меняют опросы, к которым его применяли.

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

Input Schema

NameRequiredDescriptionDefault
nameYesНазвание набора, до 40 символов.
settingsYesОбъект оформления — те же поля, что у update_workspace_report_palette.
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 readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's real contribution is the copy-semantics disclosure: the preset is a template and editing or deleting it does not mutate surveys that used it. That is meaningful behavioral context an agent cannot derive from the annotations. It stops short of covering the idempotentHint=false implication (duplicate names, repeated calls) or what the call returns.

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?

Two sentences, zero filler: the primary action and target come first, followed by the one non-obvious semantic caveat. Nothing is repeated from the title or schema.

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?

For a mutation tool with a nested settings object and no output schema, the description covers the safety-relevant semantics well but omits what is returned (preset ID?), whether names must be unique, and what the settings object accepts beyond a pointer to another tool's fields. Adequate but with clear informational gaps.

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 each parameter already documented (name ≤40 chars, settings object, workspace_id from workspace://list), so the baseline is 3. The description adds no additional parameter meaning beyond the schema, such as uniqueness constraints on name or required keys inside settings.

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 ('Сохраняет набор оформления в библиотеку аккаунта') plus its intended downstream use ('применять его к другим опросам'), so the agent knows this is a create-into-library operation rather than a palette update or a delete. It does not name a sibling such as delete_report_appearance_preset or update_workspace_report_palette, so the differentiation is implied rather than explicit.

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 via the purpose clause 'чтобы применять его к другим опросам' — i.e. use this when you want a reusable template. There is no explicit guidance on when to create a preset versus updating the workspace palette directly, nor any prerequisite or exclusion statement.

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