dForms

Change a form link

set_form_slug

Idempotent

Change the last segment of a form's public link. The old link keeps working and leads to the new one, forever, so links already shared do not break. Returns the new public_url to give the user. SLUG_TAKEN: another form of this workspace holds it (now or before), so a different slug is needed.

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_id": "<form_id>",
      "slug": "<slug>"
    },
    "name": "set_form_slug"
  }
}

Input Schema

Name	Required	Description
`slug`	Yes	The new last segment of the public link: lowercase letters, numbers and hyphens, up to 80 characters.
`form_id`	Yes	The form id, from list_forms or get_form.
`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
`form`	Yes
`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.5/5.0

Behavior5/5

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

Annotations only cover the read/write/idempotent/scope profile; the description adds genuinely new behavior: the old link forwards permanently ('forever'), and the new public_url is the intended thing to hand the user. It also spells out the SLUG_TAKEN failure condition, including that historically used slugs still block reuse — a non-obvious rule no annotation conveys.

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, ordered by importance: what changes, why it is safe, what comes back, how it fails. No filler or restatement of the title.

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?

With an output schema present, the description needn't document the response shape in detail, yet it still flags public_url as the field to relay. Combined with the SLUG_TAKEN explanation, an agent has everything needed to call this and handle the main failure.

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_id, slug and workspace_id are already fully documented, including slug format and length limits. The description adds no format or constraint 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.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a specific verb and a precisely bounded resource: 'Change the last segment of a form's public link.' That scope is narrow enough to separate it from update_form or the link-page siblings, which operate on other objects.

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 clear situational context — renaming a slug is safe because 'links already shared do not break' — which tells the agent when the call is appropriate. It stops short of naming an alternative or an explicit when-not case, so it lands just below the top band.

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?