Skip to main content
Glama

Deliveries Ebills Events

deliveries_ebills_events

Retrieves a collection of eBill events for a specified organisation and eBill, with pagination and pass-through query parameters for filtering, sorting, and field selection.

Instructions

Get a collection of ebill events. GET /organisations/{organisationId}/deliveries/ebills/{ebillId}/events

Extra query parameters (language, sort, filter, q, include, fields[...]) pass through verbatim via query.

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

Input Schema

NameRequiredDescriptionDefault
queryNo
ebill_idYes
page_limitNo
page_numberNo
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Since no annotations are provided, the description carries the full behavioral burden and successfully discloses crucial operational details about parameter handling, specifically that extra query parameters pass through 'verbatim' via the 'query' object.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The definition is highly concise and well-structured. It front-loads the purpose and immediately provides the specific API path, followed by necessary technical implementation details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the complexity of dynamic query parameters and the zero coverage of the schema, the description is contextually complete. It provides all the necessary information to make an informed decision and construct the correct API call.

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

Parameters5/5

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

With 0% schema description coverage, the description is essential. It adds rich semantic meaning to the 'query' parameter by listing specific expected parameters (language, sort, filter, etc.), which informs the agent how to structure complex requests.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the purpose: to get a collection of ebill events. This verb/resource pairing is specific and distinguishes it from related tools in the sibling list, such as `deliveries_ebills_file`.

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?

While it identifies the correct function for retrieving events, it does not provide explicit guidelines on when to use this tool versus other similar tools (like `deliveries_emails_events`), leaving usage context to the agent's inference.

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