Skip to main content
Glama

Export collected data

writ_export_data
Read-onlyIdempotent

Exports a workflow's full data table as CSV or JSON.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "writ_export_data"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNo
viewNo
formatNocsv (default) | json.
workflowNo
workflow_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / q
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / view
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / workflow
      Added value: +{
      +  "type": "string"
      +}
  2. Changed4 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"csv (default) or json"New value: +"csv (default) | json."
    • removedInput schema / properties / q
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / view
      Removed value: -{
      -  "type": "string"
      -}
    • removedInput schema / properties / workflow
      Removed value: -{
      -  "type": "string"
      -}
  3. First observed

TDQS

C2.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the safety profile is covered structurally. The description adds the format choices beyond that, but says nothing about export size limits, whether the result is inline content or a file reference, or how the workflow's data is scoped — real gaps for an export operation.

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 key action and output options come first. Its brevity is efficient, though it borders on under-specification rather than crispness.

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

Completeness2/5

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

With five parameters, zero required, no output schema, and only 20% schema coverage, the definition should explain how to select a workflow and what `q`/`view` do. It gives no return-value shape either, so an agent cannot tell whether it receives inline data, a URL, or a file handle.

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 description coverage is only 20%, with just `format` documented as "csv (default) | json." The description repeats the format idea but leaves `q`, `view`, `workflow`, and `workflow_id` — including the ambiguous distinction between `workflow` and `workflow_id` — entirely unexplained in both schema and description.

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?

"Exports a workflow's full data table as CSV or JSON" names a specific verb (exports), resource (a workflow's full data table), and output formats. It does not, however, distinguish itself from likely siblings such as writ_workflow_data or writ_search_data, leaving the agent to infer the boundary.

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 explicit when-to-use guidance, no mention of prerequisites (does the workflow need to have run?), and no reference to an alternative tool for retrieving data in other ways. The word "full" hints that filtering tools exist, but the agent must guess.

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.