Skip to main content
Glama

Close a decision

close_decision
Idempotent

Stop accepting responses. Results stay visible. 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": "close_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.8/5.0
Behavior4/5

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

Annotations already declare destructiveHint=false and idempotentHint=true, so the safety profile is covered; the description adds real value by stating "Results stay visible," which tells the agent that closing preserves existing responses rather than discarding them. "Requires the admin_token" reinforces the auth prerequisite, though it is partly redundant with the required schema field.

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?

Three short declarative sentences with zero filler, and the primary effect is front-loaded ahead of the behavioral and auth notes. Nothing is repeated and nothing could be cut without losing information.

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 simple two-parameter mutation with annotations covering safety and idempotency, the description covers effect, data retention, and auth. It does not say whether a closed decision can be reopened or what the tool returns, leaving a small gap given there is no output schema.

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%, with both decision_id (including the SettleIt link form) and admin_token fully documented in the schema. The description only restates the admin_token requirement and adds no format or edge-case meaning beyond it, so the 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?

"Stop accepting responses" is a specific verb+effect that clearly identifies this as the terminal-state action on a decision, distinguishable by implication from reopen_decision and respond_to_decision. It does not explicitly name those siblings, so an agent must infer the routing rather than read it.

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?

The intent is implied (close once you no longer want responses) but there is no explicit when-to-use or when-not-to-use guidance, and no mention that reopen_decision is the reversal path. An agent can guess correctly, but nothing in the text confirms the boundary case of closing an already-closed decision.

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