revenuebase-mcp-server

cancel_process

Stop batch email processing jobs in Revenuebase by providing the process ID to halt ongoing or queued operations.

Instructions

Cancels an ongoing or queued batch email processing job using the Revenuebase API.

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": {
      "process_id": "<process_id>"
    },
    "name": "cancel_process"
  }
}

Input Schema

Name	Required	Description	Default
`process_id`	Yes

Implementation Reference

server.py:109-125 (handler)

The main handler function for the 'cancel_process' tool. It is decorated with @mcp.tool() for registration and handles canceling a batch email processing job by making a POST request to the Revenuebase API with the process_id.

@mcp.tool()
def cancel_process(process_id: int) -> dict:
    """
    Cancels an ongoing or queued batch email processing job using the Revenuebase API.
    """
    if not api_key:
        raise RuntimeError("Environment variable REVENUEBASE_API_KEY is not set")
    url = "https://api.revenuebase.ai/v1/cancel-process"
    headers = {
        "x-key": api_key,
        "Content-Type": "application/json",
        "Accept": "application/json",
    }
    payload = {"process_id": process_id}
    resp = requests.post(url, json=payload, headers=headers, verify=False)
    resp.raise_for_status()
    return resp.json()

Schema Changelog

Changes observed during successful MCP inspections.

First observedAug 18, 2025

TDQS

C2.9/5.0

Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('Cancels') but doesn't describe what cancellation entails (e.g., irreversible, partial completion, notifications), error conditions (e.g., invalid ID, already completed), permissions required, or rate limits. This leaves significant gaps 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.

Conciseness5/5

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

The description is a single, efficient sentence with zero waste. It front-loads the key action ('Cancels') and resource, and the mention of 'Revenuebase API' provides useful context without redundancy. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity (a mutation tool with no annotations, 0% schema coverage, and no output schema), the description is incomplete. It lacks details on behavior, error handling, prerequisites, and what to expect after cancellation. For a tool that performs a potentially destructive action, this is inadequate.

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?

The schema description coverage is 0%, so the description must compensate. It implies a 'process_id' is needed by mentioning 'batch email processing job', but doesn't explain what a process_id is, where to get it, or its format. This adds minimal semantic value beyond the schema's basic structure, resulting in a baseline score.

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 clearly states the action ('Cancels') and the target resource ('ongoing or queued batch email processing job'), which is specific and actionable. It distinguishes from siblings by focusing on cancellation rather than submission, status checking, or other operations. However, it doesn't explicitly differentiate from all siblings (e.g., 'queued_process' might be related).

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., needing a valid process_id), when cancellation is appropriate (e.g., for jobs in specific states), or what happens if used incorrectly. No explicit alternatives or exclusions are provided.

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

Deploy Server