Skip to main content
Glama

Теги на ответе

tag_answer
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>",
      "answer_id": "<answer_id>",
      "tags": "<tags>"
    },
    "name": "tag_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
tagsYesМассив строковых тегов (каждый max 250 символов). Заменяет существующие теги.
quiz_idYesID опроса.
answer_idYesID ответа.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.9/5.0
Behavior2/5

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and idempotentHint=false. The description adds little beyond 'adds/synchronizes tags' and does not explain that existing tags are replaced, permissions needed, or side effects; the replacement semantics appear only in the schema.

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?

The description is a single efficient sentence with no redundant wording. The slash construction 'Добавляет/синхронизирует' is slightly ambiguous but not verbose.

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?

For a destructive, non-idempotent mutation with three required parameters, the description is minimal but the schema fully documents parameter meaning and annotations cover safety traits. It still lacks usage routing and does not state the replacement behavior in prose, leaving a moderate gap.

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 the schema itself explains that tags is a string array with max 250 characters per tag that replaces existing tags. The description adds no parameter-level meaning beyond the schema, so the baseline of 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?

The description names a specific verb ('Добавляет/синхронизирует') and resource ('теги для выбранного ответа респондента'), so the operation is identifiable. It does not distinguish this from sibling tools such as create_answer_tag or delete_answer_tag, leaving ambiguity about exact scope.

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 exclusions, and no mention of alternatives like create_answer_tag or delete_answer_tag. An agent must infer usage from the tool name and schema alone.

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