SubmitraX

Create submission export

create_export

Create a CSV or JSON export of a form's submissions, optionally filtered by date range (YYYY-MM-DD).

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": {
      "formId": "<formId>"
    },
    "name": "create_export"
  }
}

Input Schema

Name	Required	Description
`formId`	Yes	Form ID
`format`	No	Export file format
`end_date`	No	Only include submissions up to this date (YYYY-MM-DD)
`start_date`	No	Only include submissions from this date (YYYY-MM-DD)

Output Schema

Name	Required	Description	Default
`data`	Yes	Response body returned by the SubmitraX API

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedSep 29, 2026

addedInput schema / properties / end_date / description

Added value: +"Only include submissions up to this date (YYYY-MM-DD)"

addedInput schema / properties / formId / description
```
Added value: +"Form ID"
```
addedInput schema / properties / format / description
```
Added value: +"Export file format"
```

addedInput schema / properties / start_date / description

Added value: +"Only include submissions from this date (YYYY-MM-DD)"

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": false,
+  "properties": {
+    "data": {
+      "description": "Response body returned by the SubmitraX API"
+    }
+  },
+  "required": [
+    "data"
+  ],
+  "type": "object"
+}

First observedSep 28, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, and openWorldHint=true, so the safety and mutability profile is covered. The description adds only the output format choice, and says nothing about whether the export is generated synchronously or as a background job, nor about rate limits — a real gap for an export tool, but a modest one given the annotations.

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?

One sentence, front-loaded with the action and resource, with the optional filter qualifier placed last. Nothing is wasted and no reading is required to find the point.

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?

With an output schema present, full schema coverage, and annotations covering the safety profile, the description carries only a light burden. It is nearly complete, though it omits any mention of how the resulting export is retrieved, which matters given the sibling download_export.

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 all four parameters are already documented, including the YYYY-MM-DD format on both date fields and the csv/json enum. The description merely restates the format and date-range filter, adding no syntax or semantics beyond the schema, which is the baseline 3 case.

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?

The description gives a specific verb (Create) and resource (a CSV or JSON export of a form's submissions) with the optional filter dimension, so the core action is unambiguous. It does not, however, distinguish itself from nearby siblings like download_export or list_form_exports, leaving a plausible confusion unresolved.

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 when-to-use guidance, no prerequisites, and no mention of the alternative siblings (download_export, list_form_exports) that an agent would need to choose correctly. Usage is only implied by the resource itself.

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

All SubmitraX tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?