Skip to main content
Glama

Публикация опроса

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

Input Schema

NameRequiredDescriptionDefault
quiz_idYesID опроса для публикации.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare the mutation, destructive, non-idempotent and open-world profile, so the description's job is to add context. It does add one meaningful trait — that publication promotes the local version, implicitly replacing what is public — and names the tariff validation constraints, but it doesn't say what a tariff violation actually does (error vs partial publish) or whether the previous public version is preserved.

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?

Two short sentences, front-loaded with the action and its effect, with the precondition second. Nothing is redundant, though the second sentence could be tightened into an explicit failure condition.

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

Completeness4/5

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

For a one-parameter mutation with no output schema, the definition covers what changes, that a published version is involved, and the validation gate. What is missing is the outcome of a failed tariff check and whether the prior public version is overwritten, which matters given destructiveHint=true.

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 parameter whose schema description is complete, so the schema does the explaining. The description adds nothing about quiz_id beyond the schema, which is acceptable at 100% coverage but earns only baseline credit.

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 (publish a quiz) and clarifies the effect: the current local version becomes public. That is clear enough for an agent to know what the call does, though it does not name or distinguish any sibling tool.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

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

It implies a precondition for correct use — the draft must fit the tariff (question limit, allowed question types) — but gives no explicit when-to-use/when-not-to-use guidance or pointer to alternatives such as archiving or duplicating.

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