Skip to main content
Glama

Deliveries Ebills Cancel

deliveries_ebills_cancel

Cancels a pending eBill for an organisation by using the organisation ID and eBill ID in a cancel request.

Instructions

Cancel an ebill. PATCH /organisations/{organisationId}/deliveries/ebills/{ebillId}/cancel

Cancels a pending ebill; the request carries no body.

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": {
      "organisation_id": "<organisation_id>",
      "ebill_id": "<ebill_id>"
    },
    "name": "deliveries_ebills_cancel"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebill_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden and does deliver useful facts: the HTTP method (PATCH), that no body is sent, and that only pending ebills can be cancelled. It omits irreversibility, required permissions, and what the call returns, which matters 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?

Short and front-loaded: the verb-resource action comes first, then the endpoint, then the state constraint. The word 'cancel' is repeated three times across the two sentences, which is minor waste but not confusing.

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 mutation with no annotations and no output schema, the definition covers the precondition and request shape but leaves the agent guessing about the result and error behavior on a non-pending ebill.

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 compensation is needed. The path template shows both IDs are path segments, which adds a little meaning beyond the bare string properties, but neither parameter gets a description of format or where the IDs come from.

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 and resource ('Cancel an ebill') and narrows it to a lifecycle state ('Cancels a pending ebill'). It does not explicitly distinguish cancelling from the sibling deliveries_ebills_delete, so it stops short of 5.

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?

The 'pending ebill' qualifier implies when the tool applies, but the description never states what to do for a non-pending ebill or when to use delete instead of cancel. Usage is implied rather than instructed.

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