Skip to main content
Glama

Публичная ссылка на сводку

share_summary_link

Создает публичную ссылку на сводку (summary) опроса.

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": "share_summary_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
date_toNoКонец периода в формате Y-m-d (например 2024-12-31). Опционально.
quiz_idYesID опроса.
date_fromNoНачало периода в формате Y-m-d (например 2024-01-01). Опционально.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare openWorldHint=true and idempotentHint=false, so the agent knows the link is externally accessible and that repeated calls may not return the same result. The description adds only the word 'публичную' (public), without saying whether an existing link is reused or replaced, whether it expires, or who can revoke it — the exact behavior an agent needs for a share-link mutation.

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?

A single short sentence with no filler, front-loaded with the verb. It is efficiently written, though the brevity leaves little substance.

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

Completeness2/5

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

This tool creates a publicly reachable artifact and has no output schema, so the description should at minimum indicate that a link/URL is returned and how it relates to existing links. It says none of that, nor whether the date filters limit what the public link exposes.

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 quiz_id, date_from and date_to are already documented with formats and optionality. The description adds nothing about how the date range affects the shared summary (e.g. whether it scopes the exposed data), so the baseline 3 applies.

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: 'Создает публичную ссылку на сводку (summary) опроса' — an agent can tell this creates a share link for a summary. It does not differentiate from siblings like share_answers_link or share_report_link, so the resource distinction ('сводка') is the only separator.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no mention of prerequisites (permissions, whether the quiz must have answers), and no reference to alternatives such as share_answers_link or share_report_link. The agent must infer context entirely from the tool name.

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