Skip to main content
Glama

Адрес ссылки на опрос

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

Input Schema

NameRequiredDescriptionDefault
uriYesНовый адрес, от 3 до 255 символов. Лучше короткий и понятный: он попадёт в ссылку.
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial behavior beyond the annotations: taken addresses fail loudly rather than being silently replaced, and a redirect is created from the old address so already-distributed links keep working. This explains the practical consequence of destructiveHint=true rather than merely restating it, and is consistent with the declared annotations.

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?

Four short sentences, front-loaded with the action, then failure mode, then side effect, then availability constraint. Nothing is redundant and each sentence carries distinct information an agent needs before calling.

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 two-parameter mutation with full schema coverage and no output schema, this covers failure behavior, side effects, and plan gating. The only minor gap is that it does not say how the new address or the resulting redirect can be verified afterwards.

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 the baseline is 3, but the description adds meaning the schema does not: uri is only the respondent-visible portion of the link, not a full URL. It does not restate the length or readability guidance already in the schema, which is 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 — it changes the public link address of a quiz — and narrows the scope to the respondent-visible part, which is genuinely clarifying. It does not name or distinguish itself from nearby siblings such as set_share_link_active or the share_* link tools, so the agent must infer the boundary.

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

Usage Guidelines4/5

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

Gives real preconditions: the tool refuses when the address is already taken, and a custom link address is not available on every plan. What it lacks is explicit routing — it never says when to use this versus set_share_link_active or how to obtain the current address first.

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