Skip to main content
Glama

Скрытые опции вопросов

get_quiz_widgets_hidden
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_widgets_hidden"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.7/5.0
Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveness and closed-world scope, so the safety profile is fully covered elsewhere. The description contributes only the notion that the payload is 'hidden' meta-information, without saying whether hidden options are returned for all widgets of the quiz or only configured ones, or what the shape of the result is.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

One short sentence with no wasted words, which is good, but the brevity comes at the cost of specificity rather than from tight editing. There is no front-loaded detail about scope or result beyond the vague phrase 'скрытая мета-информация'.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read tool with rich annotations and a fully documented single parameter, the main missing piece is discrimination: several siblings (get_quiz_hidden_options, get_quiz_structure, get_quiz_widgets-related getters) plausibly overlap, and the description never clarifies what makes this one unique or what the returned hidden metadata consists of.

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 there is a single required integer quiz_id with a description in the schema. The description adds no meaning beyond that, which is acceptable at baseline when the schema already documents the only parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description has a concrete verb ('Возвращает') and a resource ('скрытую мета-информацию виджетов опроса'), so the general operation is legible. However, 'скрытая мета-информация' is vague — it does not say what data is actually returned (flags? visibility rules? per-widget settings?) — and nothing distinguishes it from the very close sibling 'get_quiz_hidden_options'.

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 at all: no prerequisites, no indication of when this should be preferred over get_quiz_hidden_options or update_quiz_widgets. The agent must infer the selection rule purely from the tool name.

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