Skip to main content
Glama

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

get_quiz_hidden_options
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_hidden_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.6/5.0
Behavior2/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 needs no restating. The description adds almost nothing beyond the title — only the words 'служебные' and 'конфигурации' — and says nothing about whether these options are permission-gated, what an empty result means, or how the data is shaped.

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?

It is a single short sentence with no wasted words, so it is not verbose. But the brevity comes from under-specification rather than density — nothing is front-loaded or prioritized because there is only one vague clause.

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 one-parameter read tool with rich annotations and no output schema, the definition is minimally viable — the agent knows it returns hidden quiz options. It remains unclear what 'скрытые служебные опции' contains, so an agent cannot judge the relevance of the result without calling it.

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?

There is a single required quiz_id parameter with 100% schema description coverage, so the schema already carries the parameter meaning. The description adds no format, range, or ownership constraints beyond what the schema states, which is the expected baseline-3 case.

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 gives a specific verb and resource ('Возвращает скрытые служебные опции конфигурации опроса'), so an agent knows it reads internal quiz-configuration options. However, 'скрытые служебные опции' stays abstract: it never says what these options actually are or what they control, and it draws no explicit line against the sibling get_quiz_widgets_hidden (widget-level) or the create/update/delete_hidden_option family.

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, no prerequisite (for example, that quiz_id must exist or that the options may be admin-only), and no mention of alternatives. The agent must infer from the name alone that this is the read-side counterpart to update_hidden_option.

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