dForms

List forms

list_forms

Read-onlyIdempotent

The workspace's forms, most recently updated first, each with its id, public_url and whether it has unpublished edits. It finds a form's id, and shows whether a create_form that failed or timed out went through.

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

Input Schema

Name	Required	Description
`limit`	No
`query`	No	Only forms whose name contains this text, ignoring case and accents ("contactanos" finds "Contáctanos").
`offset`	No
`workspace_id`	No	The workspace this call acts in: an id from list_my_workspaces. Required for a person signed in with several workspaces and for staff of this deployment; optional with an API key or with only one workspace.

Output Schema

Name	Required	Description
`forms`	Yes
`total`	Yes	Forms matching the query, before limit and offset.
`workspace`	Yes	The workspace this call acted in, to compare with the one the user means.
`next_offset`	Yes	Pass as offset to read the next page; null on the last page.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare this a safe, idempotent, closed-world read, so the description's added value is limited to the update-ordering ('most recently updated first') and the 'unpublished edits' flag, which is genuine behavioral context. The enumeration of returned fields is largely redundant because an output schema exists, and nothing is said about pagination or totals despite defaulting to 50 per page.

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?

Two tight sentences, front-loaded with the resource and ordering, followed by the two concrete purposes. No filler, no restatement of the tool name or title.

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-required-parameter read tool with an output schema and full annotation coverage, the description supplies what's missing on the selection and intent side. The only real gap is pagination behavior, which an agent may need to know before listing a large workspace.

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 50%: query and workspace_id are documented in the schema, while limit and offset are not. The description adds no parameter meaning at all, so it does not compensate for the undocumented half, but limit/offset are conventional, carry defaults and bounds in the schema, and the two ambiguous parameters are the ones already documented.

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 names the exact resource ('the workspace's forms'), its ordering ('most recently updated first'), and the two jobs it does: locate a form's id and verify whether a failed create_form went through. That is enough to distinguish it from get_form in practice, but it never names a sibling or states an explicit verb, so it falls short of a 5.

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 two concrete situations to reach for this tool: finding a form's id, and checking on a create_form that failed or timed out. Those are real usage conditions rather than vague context, though no exclusion or 'use X instead' routing is offered for the overlapping get_form / list_responses cases.

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

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