Skip to main content
Glama

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

get_promocode_codes
Read-onlyIdempotent

Возвращает коды конкретного списка промокодов. list_id берётся из get_promocode_list.

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": {
      "list_id": "<list_id>",
      "workspace_id": "<workspace_id>"
    },
    "name": "get_promocode_codes"
  }
}

Input Schema

NameRequiredDescriptionDefault
sortNoЧем сортировать: updated_at — по последнему изменению, name — по самому коду, id — по порядку добавления (по умолчанию).
usedNoФильтр использованных кодов: 1 — использованные, 0 — неиспользованные.
limitNoКоличество записей (по умолчанию 20).
orderNoНаправление сортировки: asc — по возрастанию, desc — по убыванию (по умолчанию).
offsetNoСмещение (по умолчанию 0).
searchNoИскать код по его тексту, частичное совпадение.
list_idYesID списка промокодов.
quiz_idNoОтобрать только коды, выданные этим опросом. Не передавать — коды всего списка.
workspace_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 readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds only the source of list_id and says nothing about pagination defaults, result size, or ordering behavior that the schema exposes but does not characterize. With rich annotations the lower bar is met, but little extra context is contributed.

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?

Two short sentences, zero filler, with the core action front-loaded and the prerequisite placed immediately after. Nothing could be removed without losing information.

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?

This is a 9-parameter read tool with no output schema, so the description should ideally say something about the shape of the returned codes (plain strings vs objects) and pagination behavior. Annotations and the fully documented schema cover most of the calling burden, but the return-value side is left entirely unspecified.

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% and every parameter including sort, order, limit, offset, search, used and quiz_id is documented inline. The description's only added meaning is where list_id comes from, which is a real but small contribution. Baseline 3 applies when the schema carries the parameter semantics.

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?

The description states a specific verb and resource: 'Возвращает коды конкретного списка промокодов' — it returns the codes belonging to one promocode list, which is distinguishable from the sibling get_promocode_list that presumably lists the lists themselves. It does not explicitly name the sibling it is not, so it stops short of a 5.

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?

'list_id берётся из get_promocode_list' gives a clear prerequisite and implies the workflow order, which is genuinely useful. However, there is no guidance on when to prefer the quiz-scoped sibling (get_promocode_list_quizzes) or on filtering choices, so usage is implied rather than spelled out.

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