Skip to main content
Glama

list_contract_deliveries

Read-onlyIdempotent

List signature request, reminder and signed-copy email delivery records, newest first. Set remindersOnly to true to return reminder attempts. Delivery times are 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_contract_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
offsetNo
remindersOnlyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.8/5.0
Behavior4/5

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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds behavior the annotations cannot: results are ordered newest first, and delivery timestamps are Unix milliseconds rather than ISO strings — a real interpetation trap avoided. It stops short of disclosing pagination behavior (page size, how offset interacts with the newest-first ordering).

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, each doing distinct work: what is returned, how to filter it, and how to read the timestamps. The most decision-relevant information (record types and ordering) is front-loaded, and there is no filler.

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 read-only, three-parameter list tool with no output schema, the description covers the essentials: contents, ordering, filtering, and timestamp format. The remaining gaps — what id identifies and how offset paginates — are modest but real for an agent that must construct the call correctly on the first attempt.

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, and it fully explains only remindersOnly — tying it to reminder attempts rather than general deliveries. The required id parameter is never described (the agent must infer it is the contract UUID from the tool name), and offset is undocumented in both the schema and the description, leaving its pagination role and interaction with maximum 100000 unexplained.

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 ... email delivery records") and enumerates the three record subtypes it returns: signature requests, reminders, and signed copies. It also states the sort order ("newest first"), which is scope information an agent can act on. It does not name or contrast itself with the sibling list_sales_document_deliveries, so the contract-vs-sales-document distinction is left to the tool name.

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: this is the tool for auditing outbound email delivery for a contract. The one explicit routing hint is "Set remindersOnly to true to return reminder attempts," which is really a parameter instruction rather than a when-to-use rule. There is no statement of prerequisites, no exclusion, and no named alternative for related questions such as reminder settings (get_contract_reminder_settings exists).

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