Skip to main content
Glama

market_request_rematch_withdraw

Withdraw a request's automatic re-matching consent now (DELETE /api/v1/marketplace/request/{id}/rematch). Matches already escrowed stay as they are.

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

Input Schema

NameRequiredDescriptionDefault
request_idYesYour marketplace REQUEST id (UUID).

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • removedInput schema / properties / request_id / title
      Removed value: -"Request Id"
    • removedInput schema / title
      Removed value: -"market_request_rematch_withdrawArguments"
    • removedOutput schema / title
      Removed value: -"market_request_rematch_withdrawDictOutput"
  2. Added

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare non-read-only, non-destructive, non-idempotent, and the description adds genuine context beyond them: already-escrowed matches are left untouched, so the agent knows the blast radius is limited to future auto-matching. It omits whether the withdrawal can be reversed (re-enabling via the sibling) and any auth requirements.

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 sentences, zero filler, with the action and its endpoint front-loaded and the side-effect caveat immediately after. Every clause earns its place.

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?

With an output schema present, return values need not be explained, and the description covers the action, endpoint, and effect on existing matches. The main residual gap is the absence of any mention of reversibility or permission requirements for a mutation tool.

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?

Only one parameter and schema coverage is 100%, so the schema already explains request_id as the marketplace REQUEST UUID. The description adds nothing further about the parameter (no format, no ownership constraint), which is the expected baseline here.

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+resource: withdrawing a request's automatic re-matching consent, reinforced by the DELETE endpoint path. It is distinguishable from the sibling market_request_rematch (the enable counterpart) through the verb 'withdraw', though it never names that 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?

'Withdraw ... now' implies immediacy, and the second sentence scopes the effect, but there is no explicit statement of when an agent should call this versus market_request_rematch or market_match, nor any prerequisites (e.g., ownership of the request).

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