Skip to main content
Glama

Опросы списка промокодов

get_promocode_list_quizzes
Read-onlyIdempotent

Показывает, к каким опросам аккаунта привязан список промокодов. Сверху идут привязанные и текущий опрос. Нужен, чтобы не отвязывать вслепую: привязку и отвязку делает manage_promocode_group.

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

Input Schema

NameRequiredDescriptionDefault
limitNoСколько опросов вернуть, от 1 до 500. По умолчанию 50.
offsetNoСколько опросов пропустить.
searchNoИскать опрос по названию.
list_idYesID списка промокодов из get_promocode_list.
quiz_idYesID опроса, от которого работаем: по нему проверяются права и тариф.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description still adds value beyond them by disclosing the result ordering (bound quizzes and the current quiz first), which affects how an agent should read the output. It stops short of describing the returned fields or whether a total count is included.

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?

Three short sentences, front-loaded with what is returned and followed by the ordering rule and the routing to the mutation sibling. No filler and nothing repeated from the schema.

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?

There is no output schema, so the description carries some burden for return shape; it covers ordering and the entity returned but not the per-item fields or pagination metadata. For a read-only filtered list with fully documented parameters and annotations, this is nearly complete.

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%, so all five parameters, including the rights/tariff check keyed on quiz_id, are already documented in the schema. The description adds no additional meaning about limit, offset, search, or list_id beyond what is structured. Baseline 3 is appropriate.

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

Purpose5/5

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

States a specific verb and resource: shows which quizzes an account's promocode list is bound to, and adds the ordering rule ('linked and current quiz come first'). It also distinguishes itself from manage_promocode_group, which performs the binding/unbinding, so an agent can separate the read tool from the mutation tool without opening either schema.

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 a concrete motivating context ('so you don't unbind blindly') and routes mutation work to manage_promocode_group explicitly. It does not spell out when the pagination/search parameters would be needed versus a plain listing, but the core when-to-use and when-not-to-use split is clear.

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