Skip to main content
Glama

list_sales_document_deliveries

Read-onlyIdempotent

List a quote or invoice's delivery records, newest first. Set remindersOnly to include only automatic invoice reminders. Timestamps use Unix milliseconds.

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": {
      "id": "<id>"
    },
    "name": "list_sales_document_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNo
remindersOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds genuinely new behavioral context beyond that: results are ordered newest first, and all timestamps are Unix milliseconds, both of which affect how an agent interprets the output. It stops short of describing pagination behavior despite an offset parameter.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with the core action and scope, followed by the one non-obvious filter and the timestamp convention. No redundant restatement of the name or annotations, and every sentence carries information the agent cannot get elsewhere.

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?

With no output schema, the description is responsible for return-value context, and it does supply ordering and timestamp units. However, for a paginated list tool (offset with a maximum of 100000) it says nothing about page size, whether more results exist, or what a delivery record contains, so an agent cannot plan iteration confidently.

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 full burden. It clarifies remindersOnly (restricting to automatic invoice reminders) and implicitly identifies id as a quote or invoice identifier, but offset is never mentioned and no pagination model is given, leaving one of three parameters and the paging contract 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 opens with a specific verb and resource: 'List a quote or invoice's delivery records,' which tells an agent exactly what is returned and what the parent entity is. It does not explicitly distinguish itself from the close sibling list_contract_deliveries, so the agent must infer that 'quote or invoice' excludes contracts, but the resource is concrete enough to route correctly in most cases.

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 resource phrasing; there is no statement of when to prefer this tool over list_contract_deliveries or when a delivery listing is appropriate versus checking status via get_sales_document_status. The only explicit conditional in the text is about the remindersOnly flag, which is parameter behavior rather than tool selection guidance.

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