Skip to main content
Glama

Belline Connect

Cancel a request

cancel_inquiry
DestructiveIdempotent

Withdraw an inquiry the person no longer wants. Works until the business has declined it or it expired; an accepted one can still be cancelled.

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": {
      "id": "<id>"
    },
    "name": "cancel_inquiry"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe id create_inquiry returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already flag destructive=true, idempotent=true and openWorld=true, so the safety profile is covered externally. The description adds real value beyond that by disclosing the state machine governing legality of the call (pending and accepted are cancellable; declined and expired are not). It does not say what happens to the inquiry record afterward or what an out-of-window call returns.

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?

Two short sentences with the purpose front-loaded and no filler. The eligibility clause is compressed into a semicolon-joined phrase that is slightly dense but still readable.

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 single-parameter mutation with no output schema, the description covers purpose and eligibility adequately. The main residual gap is failure behavior — what the agent should expect if the inquiry is already declined or expired — which matters for a destructive, open-world call.

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 100% and the sole parameter is documented in-schema as "The id create_inquiry returned." The description adds no further meaning about the id, which is acceptable given the schema already does the work — baseline 3.

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 gives a specific verb and resource: "Withdraw an inquiry" — clear about what is being acted on. It does not name or contrast with any sibling tool, so an agent must infer the boundary with tools like get_inquiry_status on its own.

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?

It states the valid window explicitly: the tool works until the business declines the inquiry or it expires, and notes that an already-accepted inquiry can still be cancelled. That is genuine when-to-use/when-not information. It stops short of naming alternatives or what to do when the window has closed.

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