Skip to main content
Glama

Правка стандартных надписей

update_quiz_texts
Destructive

Сохраняет пользовательские тексты кнопок и интерфейсных элементов опроса.

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": {
      "quiz_id": "<quiz_id>",
      "texts": "<texts>"
    },
    "name": "update_quiz_texts"
  }
}

Input Schema

NameRequiredDescriptionDefault
textsYesМассив объектов {code, text}. code — строковый ключ текста (например "button_next", "button_send"). text — новое значение (пустая строка сбросит к дефолту). Актуальные коды возвращает ресурс quiz://{id}/texts.
localeNoЯзык опроса, чьи надписи менять: код дополнительного языка из settings.languages (например "kk"). Не передан или основной язык — надписи основного языка. Меняются только переданные коды.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
      +  "description": "Язык опроса, чьи надписи менять: код дополнительного языка из settings.languages (например \"kk\"). Не передан или основной язык — надписи основного языка. Меняются только переданные коды.",
      +  "enum": [
      +    "ru",
      +    "en",
      +    "es",
      +    "pt",
      +    "de",
      +    "fr",
      +    "it",
      +    "tr",
      +    "pl",
      +    "uk",
      +    "be",
      +    "kk",
      +    "uz",
      +    "ky",
      +    "tg",
      +    "az",
      +    "hy",
      +    "ka",
      +    "ro",
      +    "cs",
      +    "nl",
      +    "sv",
      +    "fi",
      +    "da",
      +    "nb",
      +    "et",
      +    "lv",
      +    "lt",
      +    "el",
      +    "bg",
      +    "sr",
      +    "hr",
      +    "sk",
      +    "sl",
      +    "hu",
      +    "zh",
      +    "ja",
      +    "ko",
      +    "hi",
      +    "id",
      +    "vi",
      +    "th",
      +    "mn"
      +  ],
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the description carries a lighter burden, but it still adds nothing: it never warns that existing custom texts are overwritten, that an empty string resets to default, or that only the passed codes change. The single sentence essentially restates the name and title, leaving the destructive semantics entirely to annotations and 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 front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than true conciseness.

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 three-parameter mutation tool with a fully documented schema and no output schema, the definition is minimally adequate. The critical operational facts (destructive overwrite, partial update, reset-to-default, locale targeting) are present in the schema but absent from the description, which is where an agent would look first for behavioral framing.

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 schema itself explains codes, examples, the empty-string reset behavior, and the locale fallback to the primary language, so the baseline of 3 applies. The description contributes no additional parameter meaning beyond what the schema already states.

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 a specific resource ("пользовательские тексты кнопок и интерфейсных элементов опроса"), which is clear enough to distinguish it from a read-oriented sibling such as get_quiz_texts. It does not, however, explicitly contrast itself with any sibling, 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 Guidelines2/5

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

There is no when-to-use guidance: nothing says to call get_quiz_texts first to discover valid codes, nothing says this only patches the codes supplied, and nothing mentions the multi-language (locale) dimension even though that is the tool's most consequential usage decision. The agent must infer all of this from the schema.

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