Skip to main content
Glama

Deliveries Ebills Send

deliveries_ebills_send

Send an existing eBill immediately via the Pingen API by providing organisation and eBill IDs; no request body is needed.

Instructions

Send an eBill. PATCH /organisations/{organisationId}/deliveries/ebills/{ebillId}/send

Sends the eBill immediately; 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_send"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebill_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does disclose two useful traits: the send is immediate and the request carries no body. It omits the more consequential behavior an agent needs — whether sending is idempotent, what happens if the eBill was already sent or cancelled, and whether the effect is reversible.

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?

Three tight sentences, front-loaded with the action and followed by the endpoint and the no-body constraint. The raw HTTP path is slightly redundant for an agent but small and informative given the API-shaped tool set.

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-identifier action tool with no output schema, the description covers what it does and that nothing is submitted in a body. It remains thin on state transitions and failure modes, which is the main gap for a mutation with zero annotation coverage.

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% and both parameters are bare strings, so the description is the only source of meaning. It exposes the path template, which hints that organisation_id and ebill_id are path-scoped identifiers, but neither parameter is explained and their format is left entirely unstated.

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 first sentence gives a specific verb and resource ('Send an eBill'), which is cleanly distinct from the siblings that create, cancel, delete, show or list eBills. It stops short of naming an alternative, but the action is unambiguous.

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?

Usage is only implied: you call this when an existing eBill should go out. There is no statement of preconditions (must the eBill already be created or scheduled un-sent?) and no comparison to deliveries_ebills_cancel or deliveries_ebills_create, which an agent must infer.

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