Skip to main content
Glama

Deliveries Ebills Create

deliveries_ebills_create

Creates a new eBill for an organisation by sending the full JSON:API payload unchanged to the Pingen API.

Instructions

Create a new ebill. POST /organisations/{organisationId}/deliveries/ebills

payload is the full JSON:API document, sent through unchanged.

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>",
      "payload": "<payload>"
    },
    "name": "deliveries_ebills_create"
  }
}

Input Schema

NameRequiredDescriptionDefault
payloadYes
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?

No annotations are supplied, so the description carries the full burden. It does add real behavioral value by disclosing that the payload is sent through unchanged (no server-side transformation or validation) and by naming the exact POST endpoint, but it omits side effects, idempotency, permission requirements, and error behavior for a mutating operation.

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, front-loaded with the action and followed by the most decision-relevant fact about the payload. The raw endpoint path is the only near-redundant element, though it does help correlate with API docs.

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 create tool whose only substantive input is an unconstrained free-form object with no output schema, the definition should at least point to the JSON:API document shape or its required members. It conveys that the caller is responsible for the full document, which is the minimum viable signal, but leaves the agent guessing at required fields.

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 the description has to compensate. It meaningfully clarifies ``payload`` as "the full JSON:API document, sent through unchanged," which is more than the schema's opaque object/additionalProperties shape, but organisation_id is never explained and no payload field structure is given.

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 ("Create a new ebill") and pins it to an endpoint, which distinguishes it from siblings like deliveries_ebills_send, _cancel, _list, and _show. It stops short of explicitly contrasting create-vs-send, but the core purpose 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 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 (auth scopes, required org role), and no mention of when to prefer deliveries_ebills_send or batches_create instead of creating an ebill directly. The agent must infer usage from the tool name alone.

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