Skip to main content
Glama

Стандартные надписи опроса

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

Input Schema

NameRequiredDescriptionDefault
langNoЯзык служебных надписей: ru, en и прочие. По умолчанию — язык самого опроса.
localeNoДополнительный язык опроса (код из settings.languages): чьи замены вернуть. Не передан — замены основного языка.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / locale
      Added value: +{
      +  "description": "Дополнительный язык опроса (код из settings.languages): чьи замены вернуть. Не передан — замены основного языка.",
      +  "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

B3.3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is fully covered. The description adds one useful fact beyond that – that the result includes both standard and user-defined labels – but says nothing about response shape, whether missing labels fall back to defaults, or how lang/locale interact.

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 repetition. It is efficient but borders on under-specification given the two overlapping language parameters.

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, non-destructive read with full schema coverage and no output schema, the description is minimally adequate. The notable gap is that the relationship between the lang and locale parameters – the main source of ambiguity for a caller – is never addressed.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so all three parameters are already documented, and the description defers to that. It adds the notion that both standard and custom label sets come back, which lightly supports interpreting the locale parameter ('чьи замены вернуть'), though it does not explain the lang vs locale distinction itself, so it is essentially the baseline plus a small hint.

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 sentence names a specific verb ('Возвращает') and resource ('стандартные и пользовательские надписи (тексты) опроса'), which is clearly a read of quiz label texts. It is distinguishable from update_quiz_texts by the verb alone, but the description does not explicitly contrast itself with that sibling.

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 tool, when not to, or which alternative to pick. The agent must infer from the name that this is the read counterpart of update_quiz_texts; nothing in the description provides that routing.

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