Fillout MCP Server and API by Cotlet

Cotlet: how to work in an app

cotlet_app_guide

Read-onlyIdempotent

How to work in an app by clicking in the user's Cloud Browser with Cotlet's browser tools: which browser to use for this workspace and the sign-in link, the method step by step, the app's screens, menus and actions, notes, and the app's dedicated tools when Cotlet has them. Call it before the first browser step in an app. Works for any web app; one outside Cotlet's catalog gets the general method. Free, no browser session. For Fillout it covers these actions: Create form, Add question, Set form logic, Publish form, Close form, Read submissions.

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

Input Schema

Name	Required	Description	Default
`app`	No	The app's name or Cotlet slug. Default: Fillout.
`task`	No	What the user wants done in the app, in their words.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 9, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds information annotations cannot express: it is 'Free, no browser session,' which tells the agent there is no cost or live page state side effect, and that guidance for uncatalogued apps degrades to a general method.

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 lead clause is front-loaded and the trigger sentence is well placed, but the body is a long run-on enumeration of what the guide contains plus a six-item Fillout action list. Portions, especially the action enumeration, read as inventory rather than guidance useful to an agent deciding whether to call.

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 no output schema, the description usefully characterizes what the agent receives: browser selection, sign-in link, method, screens, menus, actions, and notes. Combined with the free/no-session note and default app, that is nearly everything needed to call it correctly, though the shape of the returned guide is not described.

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 coverage is 100%, with both 'app' (default Fillout) and 'task' fully documented in the schema itself. The description adds only indirect hints, such as the Fillout action list implying valid app values, so it does not meaningfully exceed the schema's own explanation.

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?

The description states a specific resource and outcome: a guide for working in an app through the Cloud Browser, covering browser choice, sign-in link, step-by-step method, screens/menus/actions, notes, and dedicated tools. It distinguishes itself from the browser_* siblings by being the pre-step briefing and from fillout_* tools by pointing at them as 'the app's dedicated tools when Cotlet has them'.

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 gives a concrete trigger: 'Call it before the first browser step in an app,' and clarifies scope ('Works for any web app; one outside Cotlet's catalog gets the general method'). It does not spell out when to skip it or how it relates to cotlet_apps for discovery, so a small gap remains.

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

All Fillout 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?