Skip to main content
Glama

Reopen a decision

reopen_decision
Idempotent

Accept responses again after closing (clears an automatic close time that has passed). Requires the admin_token.

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": "reopen_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
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. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare idempotentHint=true, destructiveHint=false and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful context: the admin_token requirement and the fact that the automatic close time is cleared. It omits what happens to an already-passed deadline or to responses collected before reopening.

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 short sentences, front-loaded with the action and followed by the mechanism and auth requirement. Nothing is wasted or padded.

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 two-parameter mutation tool with no output schema and full schema documentation, this is nearly sufficient. The only real gap is the boundary case of a manually closed decision, which affects whether the call will succeed.

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 coverage is 100% and both parameters carry their own descriptions, so the schema does the heavy lifting. The description only echoes the admin_token requirement, adding no new meaning about the decision_id format or accepted link forms.

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?

The description gives a specific verb and effect — 'Accept responses again after closing' — which is the clear inverse of the sibling close_decision. The parenthetical narrows it to clearing a passed automatic close time, though it stops short of naming close_decision explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

It implies the trigger condition (a decision that was closed, specifically by an automatic close time), but never states when not to use it — e.g. whether it works on a manually closed decision — nor points to any alternative sibling.

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