Skip to main content
Glama

postedly_delivery_report

Read-onlyIdempotent

Returns the recorded payment, fulfillment, timeline and available provider evidence for one owned order as a plain-text report, or as a PDF when format is pdf (base64 content, encoding base64). Both state what the record shows and does not show. Returns file content that can be saved privately. Evidence is provider-reported; the report is not legal proof or independent confirmation of receipt. Does not publish, share, charge or resend.

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": {
      "orderId": "<orderId>"
    },
    "name": "postedly_delivery_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
formatNotext
orderIdYes

Output Schema

NameRequiredDescriptionDefault
contentYes
orderIdYes
encodingYes
filenameYes
mimeTypeYes
recordedAtYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • addedInput schema / properties / format
      Added value: +{
      +  "default": "text",
      +  "enum": [
      +    "text",
      +    "pdf"
      +  ],
      +  "type": "string"
      +}
    • addedOutput schema / properties / encoding
      Added value: +{
      +  "enum": [
      +    "utf8",
      +    "base64"
      +  ],
      +  "type": "string"
      +}
    • removedOutput schema / properties / mimeType / const
      Removed value: -"text/plain"
    • addedOutput schema / properties / mimeType / enum
      Added value: +[
      +  "text/plain",
      +  "application/pdf"
      +]
    • changedOutput schema / required
      Previous value: -[
      -  "orderId",
      -  "filename",
      -  "mimeType",
      -  "content",
      -  "recordedAt"
      -]New value: +[
      +  "orderId",
      +  "filename",
      +  "mimeType",
      +  "encoding",
      +  "content",
      +  "recordedAt"
      +]
  2. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new context: the PDF path returns base64 file content, evidence is provider-reported and not legal proof or independent confirmation of receipt, and the report states what the record does and does not show. That is meaningful disclosure beyond the structured fields.

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?

Front-loaded with the core action and output forms, then caveats. Dense but mostly earning its place; the sentence 'Both state what the record shows and does not show' is slightly awkward and could be tightened.

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?

With an output schema present, return values need not be spelled out, yet the description still covers the base64/PDF shape and the evidentiary caveats. For a two-parameter read-only export tool this is close to complete; only the orderId ownership semantics remain thin.

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 carry the load. It does explain the format parameter well ('as a PDF when format is pdf (base64 content, encoding base64)'), but orderId is only obliquely characterized as 'one owned order' with no note on ownership scoping or failure behavior for non-owned IDs.

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 ('Returns the recorded payment, fulfillment, timeline and available provider evidence for one owned order') plus the two output forms. It is clearly a report/export tool rather than a status lookup, though it never names a sibling such as postedly_order_status to make the boundary explicit.

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 'one owned order' and the format switch, and the closing 'Does not publish, share, charge or resend' usefully rules out adjacent actions. However, there is no explicit statement of when to prefer this over postedly_order_status or postedly_orders, so the agent must infer the choice.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources