Skip to main content
Glama

Заметка к опросу

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

Input Schema

NameRequiredDescriptionDefault
notesYesТекст внутренней заметки опроса (видна только владельцу).
quiz_idYesID опроса.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=false and readOnlyHint=false, so the safety profile is covered. The description contributes the add-or-modify (upsert) nuance that the bare name update_quiz_note does not guarantee, but it never states that an existing note's text is replaced or lost, which is the key destructive behavior for a note field.

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 front-loaded sentence with no filler or repetition of the title. It is efficient, though its brevity is the cause of the missing usage and overwrite details rather than a sign of completeness.

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 two-parameter mutation with no output schema, the definition covers the essentials, and the annotations supply the safety profile. It remains incomplete on whether the supplied note replaces existing text and on how it differs from set_answer_note.

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%, with both quiz_id and notes documented, including the owner-only visibility of the note. The description adds nothing beyond that, so the baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb pair ('добавляет или изменяет') and a specific resource ('внутреннюю заметку опроса'), so the agent knows this is an upsert of a quiz's internal note. It does not distinguish itself from the sibling set_answer_note, which also deals with notes, leaving ambiguity about which note type applies.

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 guidance on when to use this tool versus set_answer_note or the other update_quiz_* siblings, and no stated prerequisites such as needing owner access. The only implied usage is the upsert semantics of 'adds or changes', which the agent must infer.

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