dForms

List my workspaces

list_my_workspaces

Read-onlyIdempotent

The workspaces this connection can act in, each with its name, your role there and its id. For a person signed in it is usually the first call before forms are read or changed: with one workspace, that one is used; with several, the user chooses one by name, and its id goes as workspace_id on every call. Staff of this deployment can act in any workspace: search finds a customer's, and the exact workspace is confirmed with the user before use, even when only one matches. With an API key it lists the key's own workspace, the only one the key can act in.

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_my_workspaces"
  }
}

Input Schema

Name	Required	Description	Default
`limit`	No	At most this many workspaces (default: every one that applies; a staff search returns at most 20).
`search`	No	Only workspaces whose name contains this text. Staff of this deployment: searches every workspace (by workspace or account name, and by a member's email or a form name where dForms knows it); needs at least 3 letters or digits and returns at most 20.

Output Schema

Name	Required	Description
`staff`	Yes	True when you are staff of this deployment and can act in any workspace.
`next_step`	Yes	The suggested next step with these workspaces.
`truncated`	Yes	True when more workspaces apply than were returned (the limit, or the staff search cap): refine the search, or raise limit.
`workspaces`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.2/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 genuinely new behavioral context: the auth model changes the result set (signed-in user vs. API key), staff can reach any workspace, and a candidate match must be confirmed before use. It does not mention pagination or response shape, but those are covered by the output schema.

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?

Dense but almost every clause earns its place, and the core answer (what is returned) is front-loaded. The single unbroken paragraph mixes return contents, selection workflow, staff behavior and API-key behavior, so splitting into short sentences would improve scanning without losing content.

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

Completeness5/5

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

Complete for a two-optional-parameter read tool: output schema exists so return values need not be enumerated, the schema documents both parameters, and the description covers the auth-dependent scope that the schema cannot express. An agent has everything needed to call it and to interpret which workspace set it will get.

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%, and both limit and search are documented in depth there, including the 20-result cap and the 3-character minimum. The description mentions search only as a staff capability and adds no syntax or filtering detail beyond the schema, so the baseline of 3 applies.

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?

States a specific resource and scope: "the workspaces this connection can act in, each with its name, your role there and its id." That is more precise than the title's restatement and tells an agent exactly what the call yields. It does not explicitly contrast with any sibling, though no sibling in the given list appears to list workspaces.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly positions the tool in the workflow: "usually the first call before forms are read or changed," then describes the one-workspace vs. several-workspace branches and how the resulting id is threaded as workspace_id. It also distinguishes the staff case from the API-key case and states when a match must be confirmed with the user.

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?