Help by DeltaBreen

update_button

Idempotent

Change a button's words, its word to type, who may press it, or turn it off or on. Give only what should change. Owner 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": {
      "button_id": "<button_id>"
    },
    "name": "update_button"
  }
}

Input Schema

Name	Required	Description
`on`	No	false turns the button off without removing it; true turns it back on.
`label`	No	New words for the button.
`button_id`	Yes	The button's id (a uuid), from list_buttons.
`word_to_type`	No	A new word to type before it runs.
`who_can_press`	No	Who may press it besides the owner: any of "admin" and "agent".
`cannot_be_undone`	No	Whether what it does cannot be undone.

Schema Changelog

Changes observed during successful MCP inspections.

Changed5 schema fields changedOct 27, 2026

changedInput schema / properties / cannot_be_undone / type

Previous value: -[
-  "boolean",
-  "null"
-]New value: +"boolean"

changedInput schema / properties / label / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

changedInput schema / properties / on / type

Previous value: -[
-  "boolean",
-  "null"
-]New value: +"boolean"

changedInput schema / properties / who_can_press / type

Previous value: -[
-  "array",
-  "null"
-]New value: +"array"

changedInput schema / properties / word_to_type / type

Previous value: -[
-  "string",
-  "null"
-]New value: +"string"

First observedOct 27, 2026

TDQS

A4/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=true, so the safety profile is covered. The description adds genuinely new context: the owner-only auth requirement, the fact that partial payloads are expected, and that "turn it off" is a reversible disable rather than a removal. It doesn't cover failure behavior for an unknown button_id.

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?

Two sentences, ~25 words, with the capability list front-loaded and the operational constraints trailing. Every clause carries information; nothing is wasted.

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

Completeness4/5

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

For a six-parameter mutation with full schema coverage, full annotations and no output schema, the description covers purpose, partial-update semantics and permissions adequately. Minor gaps remain around what happens on invalid ids or conflicting fields, but nothing an agent needs to invoke it correctly 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% and each of the six parameters is documented in-schema with more detail than the description gives. The description's phrasing mirrors the schema fields (label, word_to_type, who_can_press, on) without adding format or constraint detail, so baseline 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?

A specific verb ("Change") plus resource ("button") followed by an enumeration of the mutable facets: label, word to type, press permissions, on/off. This separates it cleanly from create_button, remove_button and press_button, though no sibling is named explicitly.

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?

"Give only what should change" is an explicit partial-update instruction, and "Owner only" states the permission prerequisite. It stops short of naming alternatives (e.g. remove_button to delete, create_button to add) or stating when an update is not appropriate.

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

All Help by DeltaBreen 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?