Skip to main content
Glama

Update Review Item

update_review_item

Edit a saved review item's topic, prompt, answer, or source while preserving its existing review schedule.

Instructions

Edits a saved review item's topic, prompt, answer, or source. Its review schedule is kept.

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": {
      "item_id": "<item_id>"
    },
    "name": "update_review_item"
  }
}

Input Schema

NameRequiredDescriptionDefault
topicNo
answerNo
promptNo
sourceNo
item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2026.11.0

TDQS

A3.7/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds a genuinely non-obvious behavioral fact beyond them: the review schedule is preserved across the edit, which tells the agent this is a partial mutation rather than a reset. It still omits permission requirements and behavior when item_id does not resolve.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the verb and resource, with the preservation caveat placed second where it belongs. Nothing is padded or redundant.

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 five-parameter mutation tool with no output schema and no annotations covering side effects, the description covers what is editable and what survives, which is the core need. It leaves the required item_id unmentioned and says nothing about partial-update semantics or failure modes, so it is adequate but not complete.

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 0%, so the description must carry the parameter meaning. It names four of the five parameters (topic, prompt, answer, source), which is useful mapping, but adds no semantics beyond the schema's own property names — it does not explain what 'source' expects or that all four fields are optional and independently editable.

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 pairs a specific verb ("Edits") with a specific resource ("a saved review item") and enumerates the mutable fields, so the agent knows exactly what changes. It is clearly distinct from delete_review_item and add_review_items by implication, though it never names a sibling to sharpen the contrast.

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

Usage Guidelines3/5

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

Usage is implied by "Edits a saved review item" and by the mention of fields, but there is no explicit when-to-use, no when-not-to-use, and no pointer to an alternative such as delete_review_item or attempt_review. The agent must infer the boundary from the verb alone.

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