Skip to main content
Glama

Новая скрытая опция опроса

create_hidden_option

Создает скрытую служебную опцию в конфигурации опроса.

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": "<name>",
      "value": "<value>"
    },
    "name": "create_hidden_option"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesКлюч скрытой опции (например "redirect_url").
valueYesЗначение опции.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior2/5

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

Annotations already declare the mutation profile (not read-only, not idempotent, not destructive). The description adds only 'hidden service option' and otherwise repeats the verb, omitting key behaviors like what happens if the key already exists, whether it requires specific permissions, or what is returned (no output schema).

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

Conciseness5/5

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

One front-loaded sentence, no filler. It is concise, though that conciseness comes at the cost of useful detail elsewhere.

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-required-parameter mutation with annotations but no output schema, the definition is minimal. It doesn't explain conflict/uniqueness behavior for 'name' or what the caller gets back, which an agent may need before invoking.

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 coverage is 100% and each parameter has a description, so the schema carries the semantics. The description names no parameters and adds no constraints beyond 'hidden option', making baseline 3 appropriate.

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?

States a specific verb ('Создает') and resource ('скрытую служебную опцию') scoped to quiz configuration, so the agent knows what it does. It does not explicitly differentiate from create_widget_hidden_option or update_hidden_option, leaving sibling selection to the name alone.

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?

No guidance on when to use this vs update_hidden_option or create_widget_hidden_option, nor prerequisites such as needing an existing quiz_id. Usage is only implied by the verb.

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