Skip to main content
Glama

update_feedback

Destructive

Update an existing feedback record by ID to change its value, weight, or metadata while keeping trace linkage immutable; use create_feedback only for new records.

Instructions

Update an existing feedback record by ID. Returns the updated status and feedback IDs, changes only value, weight, and metadata, and leaves the trace linkage immutable; use create_feedback only for a new record.

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": {
      "id": "<id>"
    },
    "name": "update_feedback"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe unique identifier of the feedback to update
valueNoNew feedback value/rating. Common patterns: 1 for positive, 0 for negative.
weightNoNew weighting factor for the feedback
metadataNoNew or updated custom metadata for the feedback

Output Schema

NameRequiredDescriptionDefault
okYesCall succeeded
dataNoSuccess payload
errorNoFailure details

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changedv0.16.5
    • changedOutput schema / properties / data / description
      Previous value: -"Structured success payload when ok is true"New value: +"Success payload"
    • changedOutput schema / properties / error / description
      Previous value: -"Structured error payload when ok is false"New value: +"Failure details"
    • changedOutput schema / properties / error / properties / details / description
      Previous value: -"Optional structured error details"New value: +"Extra error details"
    • changedOutput schema / properties / error / properties / message / description
      Previous value: -"Human-readable error message"New value: +"Error message"
    • changedOutput schema / properties / ok / description
      Previous value: -"Whether the tool call succeeded and returned structured data"New value: +"Call succeeded"
  2. Changed2 schema fields changedv1.0.9
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
  3. Addedv1.0.1
  4. Removed
  5. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Goes meaningfully beyond the annotations by naming the mutable field set (value, weight, metadata), asserting that trace linkage is immutable, and stating the returned payload (updated status and feedback IDs). It does not address permissions, what happens to omitted fields, or failure modes for an invalid ID, which is where the destructiveHint=true flag would benefit from extra context.

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?

One tight sentence that front-loads the core action and return value before the mutability constraint and the sibling reference. It is dense but every clause carries information; only the return-value mention is slightly redundant given the output schema.

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 four-parameter mutation tool with full schema coverage and an output schema, the definition covers action, mutability boundaries, and sibling disambiguation. The remaining gap is edge-case behavior — unrecognized IDs, partial metadata updates, and whether omitted fields are preserved — which an agent calling a destructive update would want.

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 already 100% with per-parameter descriptions, so the baseline is 3; the description adds real value by framing exactly which of the four parameters are mutable, implying the others are fixed. It stops short of explaining how weight interacts with value or what metadata merging semantics are.

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+resource+scope: 'Update an existing feedback record by ID'. It also implicitly contrasts with create_feedback, so an agent can distinguish the mutation path from the creation path without opening either schema.

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

Usage Guidelines4/5

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

Gives one explicit routing rule — 'use create_feedback only for a new record' — which covers the most likely confusion. It does not address other cases such as updating a record that does not exist or batching multiple updates, so it falls short of a full when/when-not matrix.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools