Skip to main content
Glama

Edit a decision

update_decision
DestructiveIdempotent

Change a decision's question and/or options after creating it. Requires the admin_token. Send only what changes.

  • question: any type.

  • options (polls and rankings): the complete new list, in display order. Use {"id": 12, "label": "New name"} to rename an option and keep its votes (ids come from get_decision), or a plain label to keep a same-named option or add a new one. Options left out are removed and their votes are deleted, so confirm with the user before dropping an option that has votes. Once someone has ranked, ranking options can only be renamed or reordered.

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": {
      "decision_id": "<decision_id>",
      "admin_token": "<admin_token>"
    },
    "name": "update_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
optionsNoComplete new option list (2-5 for polls, 2-12 for rankings).
questionNoNew question. Max 120 characters for rankings.
admin_tokenYesThe admin_token returned by create_decision.
decision_idYesDecision id or SettleIt link, e.g. "AbC123xYz9" or "https://settleit.now/p/AbC123xYz9".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the destructive annotation, the description discloses exactly what is destructive: omitted options are removed and their votes deleted, and ranked ranking options can only be renamed or reordered. It also names the admin_token requirement, adding meaningful context beyond the structured hints.

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 description is front-loaded with the core action and auth requirement, then uses a focused bullet for option semantics. The warnings are concise and earn their place by preventing destructive mistakes.

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 destructive update tool with no output schema, the description covers the critical mutation consequences, auth, and option mechanics well. It leaves some gaps, such as what the tool returns and whether closed decisions can be edited or must be reopened first.

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 description coverage is already 100%, so the baseline is 3, but the description adds valuable option semantics: the list is complete and in display order, id objects preserve votes, and plain labels preserve same-named options or add new ones. The phrase 'question: any type' is slightly imprecise against the schema's string type.

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 resource: change a decision's question and/or options after creation. It clearly separates this from create_decision and is precise enough for an agent to know this is the edit operation.

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?

The description gives clear context for use, including sending only changed fields, requiring admin_token, and confirmation before removing voted options. It does not explicitly say when not to use this tool, such as whether closed decisions require reopen_decision first.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources