Skip to main content
Glama

Change a Request

update_request
DestructiveIdempotent

Change a saved Request after the person asks or agrees.

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": {
      "request_id": "<request_id>",
      "changes": "<changes>"
    },
    "name": "update_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
changesYesOnly the fields to change; null clears one.
request_idYesThe Request’s id from list_requests.
request_keyNoOptional. The same key repeats a change safely; one is derived when left out.
expected_versionNoOptional. The Request version you last read.

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds the consent gate, which is useful context beyond annotations, but says nothing about the scope of destruction, null-clearing behavior, or version conflicts.

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?

A single front-loaded sentence with zero filler; the verb and the consent condition are the only two things stated, and both earn their place.

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?

Given a destructive nested update with an output schema and fully documented parameters, the description covers only the consent condition. It is minimally adequate because structured fields carry the rest, but it leaves an agent without guidance on destructive scope or conflict handling.

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 meanings for request_id, changes, request_key, and expected_version are already documented in the schema, including null-clears-field and idempotency semantics. The description adds no parameter-level detail, 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?

States a specific verb and resource ('Change a saved Request') and signals the target is an existing record, which implicitly separates it from save_request. It does not explicitly name a sibling or clarify how it differs from close_request, so it stops short of full differentiation.

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?

Adds a real precondition — the change happens 'after the person asks or agrees' — which tells the agent not to mutate speculatively. It gives no explicit exclusions or named alternatives (e.g., when to prefer save_request or close_request), so guidance is clear but incomplete.

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