Skip to main content
Glama

Deliveries Ebills Delete

deliveries_ebills_delete

Deletes a specified eBill from an organisation's deliveries using the organisation ID and eBill ID.

Instructions

Delete a eBill. DELETE /organisations/{organisationId}/deliveries/ebills/{ebillId}

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_delete"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebill_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

C2.7/5.0
Behavior2/5

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

With no annotations, the description carries the full burden for a destructive mutation, and it discloses almost nothing beyond the HTTP verb. It does not say whether the delete is permanent, whether it can be undone, what permissions are required, or how it differs from cancel. Only the DELETE route hints at irreversibility.

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, action first, with no filler. The endpoint restatement is mildly redundant with the tool name but serves as concrete routing detail.

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?

For a destructive, irreversible-looking operation with no annotations, no output schema, and undocumented parameters, the definition leaves too much unspecified. An agent cannot judge safety, error behavior, or the recovery path after deletion.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description would need to compensate. The path template maps organisationId and ebillId to their roles, which is a small hint, but neither parameter's format, source, or constraints are explained.

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 ('Delete a eBill') plus the exact HTTP route, so an agent knows precisely what is being removed. It does not distinguish deletion from the sibling deliveries_ebills_cancel, which is the most consequential ambiguity for an agent choosing between them.

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?

No when-to-use guidance, no prerequisites, and no mention of the alternative actions (cancel, create, show) among the many deliveries_ebills_* siblings. The agent must infer usage entirely from the tool name.

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