action1-mcp-server

Run a report and return its data or CSV export

action1_report_export

Read-onlyIdempotent

Fetch and export raw data from specified reports. Retrieve results as structured JSON rows or complete CSV blobs using the report ID or name.

Instructions

Resolve a report by name or UUID, then return JSON rows or a CSV export blob.

Input Schema

Name	Required	Description	Default
`limit`	No	Max rows when format='json'.
`format`	No	'json' rows or 'csv' blob.	json
`org_id`	No	Org UUID.
`report`	Yes	Report id or name fragment.
`response_format`	No	Output format. Default markdown.

Output Schema

Name	Required	Description
`note`	No	string
`count`	No	number
`items`	No	array
`total`	No	number
`format`	No	string
`content`	No	string
`report_id`	No	string
`truncated`	No	number \| boolean

Schema Changelog

Changes observed during successful MCP inspections.

Changed11 schema fields changedv0.6.0Oct 26, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

changedOutput schema / additionalProperties
```
Previous value: -trueNew value: +{}
```

addedOutput schema / properties / content

Added value: +{
+  "description": "string"
+}

addedOutput schema / properties / count

Added value: +{
+  "description": "number"
+}

addedOutput schema / properties / format

Added value: +{
+  "description": "string"
+}

addedOutput schema / properties / items

Added value: +{
+  "description": "array"
+}

addedOutput schema / properties / note

Added value: +{
+  "description": "string"
+}

addedOutput schema / properties / report_id

Added value: +{
+  "description": "string"
+}

addedOutput schema / properties / total

Added value: +{
+  "description": "number"
+}

addedOutput schema / properties / truncated

Added value: +{
+  "description": "number | boolean"
+}

First observedv0.5.0Jun 27, 2026

TDQS

B3.4/5.0

Behavior3/5

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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds that resolution accepts a name or UUID and that output switches between JSON rows and a CSV blob. It says nothing about the row cap, defaults, or whether the CSV path streams/blobs differently.

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?

A single front-loaded sentence with no filler; the resolve-then-return sequence is stated in order. It is efficient but arguably under-specified for a tool with five parameters rather than over-long.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so return shapes need not be explained, and annotations carry the safety profile. Remaining needs for correct invocation, resolution key and format choice, are both stated, making the definition adequate for its complexity.

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 100%, so the schema already documents all five parameters, including the format enum and limit bounds. The description corroborates 'name or UUID' resolution and the json/csv split but adds no format, syntax, or interaction details beyond the schema. Baseline 3 is appropriate.

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 chain (resolve by name or UUID, then return rows or CSV blob) on a specific resource. An agent can tell this is a combined lookup-and-fetch tool. However, it does not differentiate from close siblings such as action1_list_report_data, action1_get_export_for_report, or action1_requery_report, even though several live in the same neighborhood.

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

Usage Guidelines2/5

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

There is no guidance on when to pick this over action1_list_report_data or action1_get_export_for_report, nor on prerequisites such as report having been run already. Usage can only be inferred from the description's wording.

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

Deploy Server