Formstack MCP Server and API by Cotlet

Read submissions in Formstack

formstack_read_submissions

Read-onlyIdempotent

Read submissions in the user's own Formstack account from ChatGPT, Claude or any AI agent. Returns how to do it in Formstack step by step (screens, buttons, fields) and opens nothing by itself; then do it with the cotlet_browser_* tools in the user's Formstack Cloud Browser. Formstack's official API: Formstack has a full REST API for Forms, the V2025 API released in August 2025, but it is an add-on and Formstack publishes no MCP server for it (checked 22 Oct 2026).

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 9, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already mark this as read-only, non-destructive, idempotent, and not open-world. The description adds important behavior beyond them: it returns procedural guidance and does not perform the Formstack action itself, then requires browser tools to execute. This is valuable context that prevents the agent from assuming a direct read operation.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is generally front-loaded and clear about purpose and follow-up browser use. However, the final sentence about Formstack's official API and MCP availability is lengthy and tangential to invoking this zero-parameter tool. Phrases like "from ChatGPT, Claude or any AI agent" add audience framing without helping tool selection.

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 zero-parameter guidance tool with no output schema, the description sufficiently explains that it returns step-by-step screens/buttons/fields and that execution happens via cotlet_browser_* tools. The annotations cover safety traits. Slightly more detail about the returned guidance format would improve completeness, but the essentials are present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero input parameters, so there are no parameter semantics to explain. With no parameters and full schema coverage by definition, the baseline score is 4.

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 clearly states that the tool returns step-by-step instructions for reading Formstack submissions and explicitly says it opens nothing by itself. This distinguishes it from the cotlet_browser_* tools that must be used afterward. The opening phrase "Read submissions" could momentarily imply direct reading, but the description corrects that immediately.

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?

It tells the agent to use this tool first for guidance, then to perform the action with cotlet_browser_* tools in the user's Formstack Cloud Browser. That gives clear when-to-use routing and an explicit alternative for execution. It lacks explicit when-not-to-use conditions, but the separation between guidance and browser execution is clear.

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

All Formstack MCP Server and API by Cotlet 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?