Skip to main content
Glama

Тема оформления

get_theme_details
Read-onlyIdempotent

Возвращает детальные настройки темы оформления (цвета, фон, кнопки и др.).

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": {
      "theme_id": "<theme_id>"
    },
    "name": "get_theme_details"
  }
}

Input Schema

NameRequiredDescriptionDefault
theme_idYesID темы.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds only the content of the payload (colors, background, buttons), with no mention of error behavior for unknown theme_id or whether the response is a fixed schema.

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?

A single short sentence with the resource and payload contents front-loaded and no filler. It could not be trimmed further without losing the field examples, though it is minimal rather than rich.

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 simple one-parameter read tool with rich annotations this is close to sufficient, but with no output schema the description is the only source of return-shape information and it offers only 'цвета, фон, кнопки и др.' – a non-exhaustive, open-ended hint rather than a defined structure.

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% for the single parameter theme_id ('ID темы.'), so the schema carries parameter documentation. The description adds no format, sourcing, or validation detail beyond that, which is the expected baseline for a one-parameter tool.

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 verb ('Возвращает') and resource ('детальные настройки темы оформления'), and even enumerates the kinds of data returned (цвета, фон, кнопки). It is clearly a single-theme read, distinguishable from a list-style sibling, but it never names an alternative tool to reinforce that distinction.

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

Usage Guidelines2/5

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

There is no statement of when to use this versus get_theme_list, update_theme, or manage_theme, nor any prerequisite (e.g., that a theme_id must first be obtained from a list call). The agent must infer usage from the name alone.

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