Skip to main content
Glama
Sign In

dForms

by ai.dforms.mcp
OverviewDiscussionsAdmin

Undo the brand kit on forms

revert_brand_kit
DestructiveIdempotent

Give these forms back the look they had before apply_brand_kit (their themePreset included), live at once. Destructive: it deletes or replaces data, so it is best confirmed with the user first, naming exactly what will change. After an error or a timeout, a read shows whether the change went through, so a blind retry is not needed. Owners and admins only.

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": {
      "form_ids": "<form_ids>"
    },
    "name": "revert_brand_kit"
  }
}

Input Schema

NameRequiredDescriptionDefault
form_idsYesThe forms, 1 to 500 ids from list_forms.
workspace_idNoThe 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

NameRequiredDescriptionDefault
revertedYesThe forms put back. A form the kit was never applied to is skipped.
workspaceYesThe workspace this call acted in, to compare with the one the user means.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare destructiveHint, idempotentHint and openWorldHint, yet the description adds genuinely new context: the change is immediate ('live at once'), it deletes or replaces data, user confirmation naming the exact changes is advised, and permissions are restricted to owners/admins. It also explains the safe recovery path after a timeout, which the annotations cannot express.

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?

Four short sentences, front-loaded with the action and immediacy, then destructive-safety, recovery, and access restriction in order of operational importance. No sentence is redundant.

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?

For a destructive, idempotent mutation with an output schema, everything an agent needs is present: what it reverses, immediacy, safety confirmation, recovery after failure, and permission requirements. Return-value detail is correctly omitted since an output schema exists.

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 form_ids and workspace_id are already fully documented in the schema, and the description only reinforces the plural 'forms' framing. It adds no meaning about the workspace_id conditional requirement or the id format beyond what the schema states.

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 uses a specific verb and resource ('give these forms back the look they had before apply_brand_kit') and names the exact operation being undone, including the detail that themePreset is restored. An agent can immediately tell this is the inverse of apply_brand_kit rather than a generic brand-kit edit.

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 clearly states the trigger (undoing a prior apply_brand_kit), the prerequisite (owners and admins only), and the correct handling after errors or timeouts (read before retrying). It stops short of stating when not to use it or which sibling to pick for a narrower scope, so an exclusion clause is the only gap.

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

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