Skip to main content
Glama

Список публичных ссылок

get_share_links
Read-onlyIdempotent

Список публичных ссылок на сводку, отчёт или ответы опроса — сначала новые, вместе с выключенными. У каждой ссылки: uuid, номер по порядку создания (number), адрес (url), дата создания (created_at), работает ли она (is_active), у ответов — сколько ответов в ссылке (answers_count, null — все ответы). total — сколько всего ссылок у раздела. Ссылки респондентов на свой ответ в список не входят.

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

Input Schema

NameRequiredDescriptionDefault
limitNoСколько самых новых ссылок вернуть, от 1 до 100. По умолчанию 100.
quiz_idYesID опроса.
sectionYesРаздел: summary — сводка, report — отчёт, answers — ответы.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description does add genuinely useful behavior beyond that: ordering (newest first), that disabled links are still returned, and that respondent self-links are excluded. It does not cover pagination beyond limit or what happens with an invalid section/quiz_id, so it is solid but not rich.

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?

Front-loaded with purpose and ordering, then a compact field inventory; nearly every clause carries information. The middle field list is dense and slightly run-on, but nothing is padding.

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, and the description compensates well by enumerating every returned field (uuid, number, url, created_at, is_active, answers_count, total). Only error/failure behavior and any pagination interplay between limit and total are left unaddressed.

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 a baseline of 3 applies; the description adds meaning on top by clarifying that limit selects the newest links ("сначала новые") and by explaining that answers_count can be null meaning "all answers". The section values are repeated rather than extended, which keeps this from a 5.

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 opens with a specific verb+resource ("Список публичных ссылок на сводку, отчёт или ответы опроса") and scopes it to the three section values, plus an explicit exclusion ("Ссылки респондентов на свой ответ в список не входят"). It is clearly a read/list operation, but it never names the sibling creation tools (share_summary_link, share_report_link, set_share_link_active), so the boundary with those is left implicit.

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?

Usage is only implied by the list semantics and the section parameter; there is no explicit "use this when…" or "use X instead for…" statement. The exclusion of respondent links does narrow the scope usefully, but no prerequisites (e.g. that quiz_id must exist) or guidance about when to refresh this data are given.

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