Skip to main content
Glama

Deliveries Ebills Events Image

deliveries_ebills_events_image

Retrieves the image URL for a specific eBill delivery event and returns the redirect response without following it, enabling inspection or processing of the image location.

Instructions

Get an image of an ebill event. GET /organisations/{organisationId}/deliveries/ebills/{ebillId}/events/{deliverableEventId}/image

Answers 302 to the image; 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>",
      "deliverable_event_id": "<deliverable_event_id>"
    },
    "name": "deliveries_ebills_events_image"
  }
}

Input Schema

NameRequiredDescriptionDefault
ebill_idYes
organisation_idYes
deliverable_event_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the key non-obvious behavior: the upstream answers 302 and the tool returns a {"redirect_url", "status_code"} envelope without following it. That is genuinely useful, though it omits auth requirements and error behavior.

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 sentences, front-loaded with the purpose before the endpoint, and the redirect caveat follows immediately. The raw path template is somewhat redundant with the parameter names but is compact and helps map parameters to path segments.

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 three-path-parameter read tool with no annotations and no output schema, the description covers the essential gap by explaining the returned envelope. Missing only auth/permission context and failure modes to be fully self-sufficient.

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% across three required parameters, so the description must compensate. It partially does by embedding the URL template, which clarifies that organisation_id, ebill_id, and deliverable_event_id are positional path parameters, but it adds no format or validity constraints for any of them.

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 an image of an ebill event') plus the exact endpoint path, which distinguishes it from the events-listing sibling and from the email-image variant. It stops short of naming those alternatives, but the resource specificity is enough for an agent to select it.

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 only implied by the noun phrase 'image of an ebill event' - an agent can infer this is the tool for retrieving event imagery, but there is no explicit when-to-use statement, no prerequisites, and no named alternative for related needs.

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