Skip to main content
Glama

conduyt_export_report

Export a saved report's matching rows as CSV or XLSX text (up to 50,000) for analysis or delivery, narrowing filters when a report is too large.

Instructions

Export every matching row of a saved report (up to 50,000) as CSV or XLSX text. Returns the file body; for a large report narrow the filters or ask for the scheduled delivery.

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": "conduyt_export_report"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYes
formatNocsv (default) or xlsx

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv4.71.0

TDQS

A3.6/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 behavioral burden. It usefully discloses the 50,000-row cap and that it returns the file body, but omits permissions, rate limits, and whether the export is synchronous or subject to timeouts.

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?

Two compact sentences with no wasted wording. The core action and cap are front-loaded, and the large-report guidance follows naturally.

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 simple two-parameter export tool with no output schema, the description gives the essential return shape, row cap, and large-report alternative. It is nearly complete, though it could name the scheduled-delivery tool and clarify the id parameter.

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 coverage is only 50%: format is documented in the schema, while id is not. The description implies id refers to a saved report and adds output-format context, but it does not fully compensate for the undocumented required id parameter.

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: export every matching row of a saved report as CSV or XLSX. It is clear what the tool does, but it does not explicitly differentiate itself from report siblings such as run_report or preview_report.

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?

Gives a useful constraint and fallback for large reports: narrow filters or use scheduled delivery. However, it does not state when to choose this over run_report, preview_report, or other export tools, so usage is implied rather than fully guided.

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