Skip to main content
Glama

Deliveries Ebills File

deliveries_ebills_file

Retrieves the stored PDF file for an eBill and returns its redirect URL and status code without following the redirect.

Instructions

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

Answers 302 to the stored PDF; returns the {"redirect_url", "status_code"} envelope without following the redirect.

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

Input Schema

NameRequiredDescriptionDefault
ebill_idYes
organisation_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior4/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 and does well on the most important trait: it discloses that the endpoint answers 302 and returns a {"redirect_url", "status_code"} envelope rather than the PDF bytes because the redirect is not followed. That is exactly the kind of fact an agent cannot infer from the schema. It omits auth requirements and error behavior, keeping it from a 5.

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, the core action and route front-loaded, followed by the crucial redirect caveat, with no filler. The phrasing 'Get file of ebill' is slightly awkward but costs no clarity.

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?

For a two-parameter read endpoint with no annotations and no output schema, the description covers the essential unknown — that the caller receives a redirect envelope, not the file. Missing pieces are comparatively minor: authentication expectations and failure modes.

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%, so the description must supply parameter meaning, and it only indirectly does so via the path template /organisations/{organisationId}/deliveries/ebills/{ebillId}/file. There is no statement of format, expected ID shape, or what happens if either required identifier is wrong, leaving both parameters largely undocumented.

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 description gives a specific verb and resource ('Get file of ebill') plus the exact REST route, which pins down the tool's scope unambiguously. It does not, however, mention when to prefer it over the near-identical file-fetching siblings like deliveries_emails_file or letters_file, so it falls short of the sibling-differentiation bar for a 5.

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 implied by the narrow purpose and by the required ebillId/organisationId pair, but there is no explicit 'use this when…' or 'do not use for…' statement. The presence of parallel file tools for emails and letters makes the missing routing guidance a real gap.

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