RetailHardHat

Export Report

export_report

Read-onlyIdempotent

Export an authorized report as CSV, Excel XLSX or PDF. Discover datasets with get_report_registry first. Returns a downloadable MCP embedded file, never a public or signed URL. allPages reads up to maxRows (default 500, hard cap 1000 or a lower organization/connection policy). Always disclose truncation. Every page rechecks permissions and masking. Requires explicit export permission. MCP approval requirements are configurable by the organization administrator; business workflow approvals always apply.

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": {
      "name": "<name>",
      "args": "<args>"
    },
    "name": "export_report"
  }
}

Input Schema

Name	Required	Default
`args`	Yes
`name`	Yes
`format`	No	csv
`maxRows`	No
`allPages`	No

Output Schema

Name	Required	Description	Default
`data`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 27, 2026

TDQS

A4.3/5.0

Behavior5/5

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

Despite annotations already covering the safe-read profile, the description adds substantial non-obvious behavior: page-by-page permission rechecks and masking, mandatory truncation disclosure, the 500/1000 row policy caps, the absence of public/signed URLs, and org-configurable approval requirements.

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 purpose and format, then constraints. Dense but every sentence carries information; the approval-requirements sentence is the least essential but still behavioral context.

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?

Return-value explanation is rightly omitted given an output schema, and permission/truncation/approval behavior is covered. The gap is the required `name`/`args` pair, whose expected shape an agent cannot derive from either schema or description.

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?

With 0% schema description coverage the description must compensate. It handles format, maxRows (default 500, cap 1000, policy may lower) and allPages semantics well, but says nothing about the two required parameters `name` and `args`, which are the highest-risk inputs (the nested args object is entirely opaque).

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Export an authorized report') plus the output formats (CSV/XLSX/PDF) and the delivery mechanism (MCP embedded file, not a URL). This is clearly distinguishable from siblings like run_report and get_report_registry.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly names a prerequisite and alternative: 'Discover datasets with get_report_registry first.' It gives a clear when-to-use path but does not contrast with the close sibling run_report (data vs. file export), leaving one routing decision to inference.

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

All RetailHardHat tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?