Skip to main content
Glama
Sign In

Youform

by io.github.mkmaker
OverviewDiscussionsAdmin

Update block

update-block-tool
Destructive

Update a draft block. Send only the fields you want to change; omitted fields keep their current values. Changing type starts with the new type's defaults. Options, rows and columns replace their entire lists: preserve existing ids when editing labels; new items receive ids in the response. Only text blocks can be endings (is_last true), and at least one ending must remain. Use set-block-logic-tool to change rules or default_transition. Use add-block-tool with group_id to add questions inside a group; group membership cannot be changed here.

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_slug": "<form_slug>",
      "block_id": "<block_id>",
      "block": "<block>"
    },
    "name": "update-block-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
blockYesFields to change, following the structure from get-form-tool / list-block-types-tool. Omitted fields are preserved; option/row/column lists are replaced.
block_idYesThe id of the block to update, from get-form-tool.
form_slugYesThe form's slug.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true, and the description adds the concrete reason: option/row/column lists are replaced wholesale rather than merged, which is exactly the data-loss risk an agent needs to know. It also discloses that omitted fields are preserved, type changes reset to the new type's defaults, and new items receive ids in the response. Missing only error-shape or permission details, which is minor here.

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?

Six short sentences, no filler, front-loaded with the partial-update rule before the destructive list semantics and the sibling routing. Every sentence carries a distinct operative constraint.

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?

No output schema exists, and the description compensates by explaining that new items receive ids in the response. For a nested-object mutation tool with 100% schema coverage and destructive annotations, the description supplies everything an agent needs to call it correctly and safely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds real meaning to the nested `block` object: partial-update semantics, the replace-not-merge rule for lists, id preservation for existing items, and that new items get ids back. It does not enumerate block fields, though it points to get-form-tool / list-block-types-tool for the structure.

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 ('Update a draft block') and immediately bounds scope: partial field updates, type changes, and list replacement are all named. It also names the sibling tools it is not (set-block-logic-tool, add-block-tool), so an agent can route correctly without opening schemas.

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?

Explicit routing rules: use set-block-logic-tool for rules or default_transition, use add-block-tool with group_id to add questions in a group, and group membership cannot be changed here. Constraints on validity ('Only text blocks can be endings', 'at least one ending must remain') tell the agent when a call will fail.

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

All Youform 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