Skip to main content
Glama

Get decision results

get_decision
Read-onlyIdempotent

Read a decision and its current results: votes and leaders for polls, rankings with points, In/Maybe/Out names for check-ins, and per-slot counts plus best_slot_ids for availability. Also returns the option or slot ids that respond_to_decision needs.

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>"
    },
    "name": "get_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
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

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description adds substantive content beyond that by spelling out the shape of returned data per decision type, which is valuable given there is no output schema; it does not cover error behavior for malformed or unknown ids.

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, front-loaded with the core action, then a compact enumeration of result shapes. The itemized list is dense rather than padded, and the closing sentence about respond_to_decision earns its place by linking to a sibling tool.

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?

With no output schema, the description carries the return-value burden and does so across all four decision types, which is the main thing an agent needs. Minor gaps remain around failure modes for invalid ids or links, but nothing essential for correct invocation 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?

There is a single parameter with 100% schema description coverage, including the accepted id-or-link formats, so the schema does the heavy lifting. The description adds no further meaning about decision_id, which matches the baseline of 3 for fully documented parameters.

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 ('Read a decision and its current results') and then enumerates exactly what those results look like for each decision type (poll votes/leaders, rankings with points, In/Maybe/Out for check-ins, per-slot counts and best_slot_ids for availability). It also distinguishes itself from the sibling respond_to_decision by noting it supplies the option/slot ids that tool needs.

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?

Gives clear implied context for use: call this to inspect results, and call it first when you need the option or slot ids required by respond_to_decision. It does not state any when-not conditions or contrast with other read paths, but the sequencing guidance is concrete.

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