Skip to main content
Glama

Deliveries Ebills List

deliveries_ebills_list

Retrieve a paginated list of eBills for an organisation, with query parameters for sorting, filtering, and field selection. Supports page limits and numbering for manageable API results.

Instructions

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

Extra query parameters (sort, filter, q, include, fields[...]) pass through verbatim via query; page_number/page_limit map to page[number]/page[limit].

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

Input Schema

NameRequiredDescriptionDefault
queryNo
page_limitNo
page_numberNo
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.3/5.0
Behavior3/5

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

With no annotations supplied, the description carries the full behavioral burden. It usefully discloses the underlying HTTP GET endpoint and how pagination params are rewritten into the wire format, but it says nothing about result-set limits, default page size, ordering, or permission requirements for the organisation.

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 tight sentences, with the purpose and endpoint front-loaded before the parameter mechanics. Every sentence carries information; no filler or redundant restatement of the title.

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 read-only list endpoint with no annotations and no output schema, the definition covers the input side well but leaves the return side and permission model implicit. It is adequate to invoke the tool, less adequate to predict what comes back.

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

Parameters4/5

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

Schema coverage is 0%, so the description must compensate, and it largely does: it names the sort/filter/q/include/fields families that flow through ``query`` and maps ``page_number``/``page_limit`` to the API's ``page[number]``/``page[limit]``. Only ``organisation_id`` goes unexplained.

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 ("Get a collection of ebills") plus the concrete endpoint path, and the word "collection" distinguishes it from the singular deliveries_ebills_show sibling. It stops short of naming that sibling, so an agent still has to infer the split.

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?

There is no explicit when-to-use or when-not-to-use guidance and no alternative listed; the only steer is the implicit 'list vs. show' reading of 'collection'. An agent must decide on its own whether to call this or deliveries_ebills_show/create.

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