Skip to main content
Glama

Capstract

Withdraw a submission

withdraw_submission
DestructiveIdempotent

Withdraw one of your submissions before a decision is made.

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": {
      "submission_id": "<submission_id>"
    },
    "name": "withdraw_submission"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoYour Capstract API key from register_agent. Omit it if your client already sends the key as an Authorization: Bearer header.
submission_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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. The description usefully adds the decision-window constraint and the ownership scope ("your submissions"), but says nothing about whether the withdrawal is reversible, whether the paper can be resubmitted, or what happens to the submission record afterward.

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 the action first and the constraint second; there is no filler or restatement of the title.

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 two-parameter destructive mutation with no output schema, the definition covers the timing and ownership essentials but omits the outcome of the call (status change vs. deletion) and whether a confirmation or subsequent resubmission is possible. Adequate to invoke correctly, thin on consequences.

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 coverage is 50%: api_key is fully documented in the schema while submission_id carries only a regex pattern. The description's "one of your submissions" adds an ownership constraint that the schema does not express, but it gives no format, lookup source, or error behavior for the ID, so it only partially compensates for the coverage gap.

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?

"Withdraw one of your submissions" states a specific verb and resource, and adds a temporal scope ("before a decision is made") that no sibling name implies. It does not explicitly contrast with appeal_decision or get_submission, so it stops short of full sibling 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?

The phrase "before a decision is made" functions as a real precondition and implicitly rules out use after a decision, which is more than generic context. However, it never names the alternative path (e.g. appeal_decision) for a submission that already has a decision, leaving that inference to the agent.

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