Skip to main content
Glama

conduyt_report_schedule_deliveries

Retrieve a report schedule's delivery history, including status, row counts, email delivery, and file download URLs, to verify past runs and troubleshoot failed deliveries.

Instructions

The delivery history of a schedule (newest first): status, rows, whether it was emailed, and download URLs for the files.

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": {
      "sid": "<sid>"
    },
    "name": "conduyt_report_schedule_deliveries"
  }
}

Input Schema

NameRequiredDescriptionDefault
sidYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

B3.4/5.0
Behavior3/5

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

With no annotations, the description carries full burden but does disclose meaningful behavior: ordering is newest-first and the payload includes status, row count, email-failure indicator, and file URLs. It omits pagination/result limits, what happens for a schedule that has never run, and whether the download URLs expire — relevant for a no-annotation tool.

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?

A single sentence that front-loads the resource, then lists the returned fields with the sort order tucked into parentheses. No redundant or marketing language.

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 one-parameter read tool with no output schema and no annotations, describing the returned fields and ordering covers most of what an agent needs to call it and interpret results. The gap is the total absence of parameter guidance and any note on result volume/pagination.

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 coverage is 0%, so the description must compensate for the single required parameter, but it never mentions `sid` at all — only the vague phrase 'of a schedule'. An agent must infer that sid is the schedule identifier, and gets no guidance on ID format, source of the ID, or error behavior for unknown 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 resource (delivery history of a schedule) and enumerates what it contains (status, rows, emailed flag, download URLs), so an agent can tell it apart from list_report_schedules or send_report_schedule_now. It is a noun phrase rather than a verb, and no sibling is named, so it stops short of 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?

The read-only nature of 'history' implies when to reach for it, but there is no explicit statement of when to use this versus list_report_schedules or run_report, and no prerequisites (e.g., schedule must exist and have fired at least once).

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

Deploy Server

Other Tools