Skip to main content
Glama

revise_work_request_response

Revise your current proposal or decline while demand is open. Provide expectedTermsHash and new kind/terms. Old versions remain public; selection freezes the selected version. Requires merchant:manage.

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": {
      "requestId": "<requestId>",
      "responseId": "<responseId>",
      "revision": "<revision>"
    },
    "name": "revise_work_request_response"
  }
}

Input Schema

NameRequiredDescriptionDefault
revisionYes
requestIdYes
responseIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full load and does disclose meaningful traits: the auth scope requirement ('Requires merchant:manage'), that prior revisions stay publicly visible, and that selection freezes the chosen version. It does not cover what happens when expectedTermsHash is stale or whether the call is idempotent, leaving a gap for a mutation 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 required inputs, then the retention semantics and the auth scope. Nothing is padded, though 'Provide expectedTermsHash and new kind/terms' partially restates what the schema enforces.

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 mutation with a deeply nested, branch-dependent schema and no output schema or annotations, the description covers the essentials an agent needs: auth scope, immutability of prior versions, selection-triggered freezing, and the concurrency token. It stops short of describing failure modes on hash mismatch, which is the main remaining gap.

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 compensate, and it only names two of the three parameters ('expectedTermsHash and new kind/terms') without explaining that expectedTermsHash is a stale-write guard or how terms differ between the proposal and decline branches. The schema itself is heavily constrained with consts and enums, so the agent can still call it correctly, but the description adds little semantic depth.

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 uses a specific verb ('Revise') on a specific resource ('your current proposal') and also covers the alternate outcome ('or decline'), which distinguishes it from propose_work_request and decline_work_request since it operates on an existing response. The gating condition 'while demand is open' further narrows the operation, though it does not name a sibling explicitly.

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?

'while demand is open' supplies a real precondition for use, but there is no explicit when-not guidance and no named alternative (e.g., that a fresh bid should go through propose_work_request and a first refusal through decline_work_request). Usage is implied rather than directed.

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