Skip to main content
Glama

Пометка у ответа

set_answer_note
Destructive

Ставит короткую пометку у отдельного ответа респондента — «перезвонить», «дубль», «жалоба». До 100 символов. Пустое значение снимает пометку. Это не заметка к опросу целиком (та в update_quiz_note) и не тег (те в tag_answer).

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

Input Schema

NameRequiredDescriptionDefault
noteNoТекст пометки, до 100 символов. Пусто — снять пометку.
quiz_idYesID опроса.
answer_idYesID ответа из quiz://{id}/answers.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false and destructiveHint=true; the description adds useful context that an empty value removes the note and that the payload is capped at 100 characters. It does not say whether setting a new note overwrites an existing one or what the call returns, which is the remaining gap on a mutating tool.

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?

Four short sentences, front-loaded with the action and followed by the constraint, the removal case, and the disambiguation. No filler, though the sibling-disambiguation clause is dense and could be split more cleanly.

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?

For a 3-parameter, no-nested, no-output-schema tool with full schema coverage and annotations covering the safety profile, the description supplies almost everything an agent needs. Only the overwrite semantics and response shape are left implicit.

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, answer_id and note are all documented in the schema, including the 100-char cap and the null-means-clear behavior. The description's only added value is illustrative example note values, which is marginal rather than additive.

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 ("Ставит короткую пометку у отдельного ответа респондента") with concrete examples of the note values, and explicitly names what it is not (a quiz-level note, a tag) while pointing at the siblings that do those things.

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

Usage Guidelines5/5

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

Gives explicit routing rules: per-answer note goes here, whole-quiz note goes to update_quiz_note, tagging goes to tag_answer. It also states the removal case (empty value) which is the main alternate invocation mode.

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