Skip to main content
Glama

Deliveries Ebills Show

deliveries_ebills_show

Fetch details for a specific eBill within an organisation, with optional query parameters for included fields and related data.

Instructions

Get details of an ebill. GET /organisations/{organisationId}/deliveries/ebills/{ebillId}

query keys (include, fields[...]) pass through verbatim.

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

Input Schema

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

No annotations are supplied, so the description carries the full burden. It does disclose the underlying GET, which tells the agent this is a non-mutating fetch, and it explains that ``query`` keys pass through verbatim rather than being interpreted. It says nothing about error behavior, whether the ebill must exist, or what happens with unsupported query keys.

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, purpose first, then the endpoint and the one non-obvious parameter behavior. Nothing is padded, though the raw path partly restates the parameter names.

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

Completeness4/5

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

A three-parameter read tool with no output schema and no annotations is largely covered: purpose, endpoint, and the only unusual parameter (query) are explained. The remaining gap is that nothing indicates what fields the returned ebill details contain, which matters given the absent output schema.

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 must compensate. It usefully explains the opaque ``query`` object — pass-through keys such as include and fields[...] — but adds nothing about ebill_id or organisation_id beyond what the path template already reveals.

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 details of an ebill', backed by the exact endpoint path. That clearly separates it from siblings like deliveries_ebills_list (many) and deliveries_ebills_delete/cancel (mutations), though the description never explicitly names those distinctions.

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 or when-not-to-use guidance is given. The required ebill_id implies a single-record lookup, but the description never tells the agent to prefer this over deliveries_ebills_list when it already has an id, nor what to do if the id is unknown.

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