dForms

Apply the brand kit to forms

apply_brand_kit

DestructiveIdempotent

Put the brand kit on these forms, live at once, published or not: their own logo, colours and type are replaced by the kit, and their themePreset (the editor's note of the last preset picked) is cleared, because it no longer describes their colours. revert_brand_kit brings back the look each form had before. 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": "apply_brand_kit"
  }
}

Input Schema

Name	Required	Description	Default
`form_ids`	Yes	The forms, 1 to 500 ids from list_forms.
`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	Default
`applied`	Yes	The forms the kit was applied to. Ids of other workspaces are skipped, and nothing applies without a kit.
`workspace`	Yes	The workspace this call acted in, to compare with the one the user means.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 13, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already flag destructiveHint and idempotentHint, but the description goes further by naming the specific data that is overwritten (logo, colours, type) and cleared (themePreset). It also discloses the authorization requirement and the error/timeout recovery path — read to check whether the change landed rather than blindly retrying.

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?

The destructive scope and the data that changes are front-loaded before the alternative tool and the recovery advice. Dense but every clause carries information an agent needs; nothing is padding.

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 bulk mutation the description covers scope, side effects, permissions, confirmation posture, and failure recovery, and an output schema exists so return values need not be explained. Nothing an agent needs to call this safely is missing.

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 both parameters are already documented in the schema, including the 1–500 id range and the workspace_id conditional. The description only refers to "these forms" and adds no syntax, ordering, or partial-failure semantics beyond that baseline.

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?

States a specific verb and resource ("Put the brand kit on these forms") and enumerates exactly what changes: logo, colours and type are replaced and themePreset is cleared. It also explicitly distinguishes itself from revert_brand_kit, so an agent can route between the two without opening either schema.

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?

Gives the use condition (apply to forms, published or not), the inverse operation to reach for instead (revert_brand_kit restores the prior look), a prerequisite (owners and admins only), and procedural guidance (confirm with the user first, naming exactly what will change). Little is left to inference.

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?