Skip to main content
Glama

Create a group decision

create_decision

Create a poll, check-in, availability board, or ranking and get a link to share with the group.

Easiest: pass text in plain language and SettleIt infers the type and options, e.g. "Dinner: pizza or thai" (poll), "Who's in for bowling Thursday?" (checkin), "Find a time for dinner next week" (availability), "Rank snacks: chips, popcorn, pretzels" (ranking). For exact control, pass question plus options (2-5 for polls, 2-12 for rankings); with question alone you get a check-in. Availability must be created from text. For availability, also pass the user's timezone (IANA name, e.g. "America/Los_Angeles") so the time slots are in their local time; without it slots are in UTC.

Returns the decision (share its url), plus an admin_token and manage_url to keep private.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_decision"
  }
}

Input Schema

NameRequiredDescriptionDefault
textNoPlain-language prompt. Max 200 characters except rankings.
typeNoForce a type. Optional with text.
optionsNoUnique choices, used with question.
questionNo
timezoneNoAvailability: the user's IANA time zone, e.g. "America/Los_Angeles". Slots and words like "tomorrow" use it. Defaults to UTC.
closes_in_minutesNoPolls only: auto-close after this many minutes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly=false, destructive=false, idempotent=false, openWorld=true, so mutation and safety are covered. The description adds real value beyond that by disclosing the return payload (`url`, plus `admin_token` and `manage_url` to keep private) and the timezone default of UTC. It stops short of warning that repeated calls create duplicate decisions or noting any rate limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the one-line purpose, then the easiest path, then exact control, then caveats, then return values — a sensible ordering with no filler sentences. Slight redundancy in repeating the availability/`text` requirement and a fairly dense second paragraph keep it from a 5.

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

Completeness5/5

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

For a 6-parameter creation tool with no output schema, the description covers input precedence, type-specific constraints, timezone handling, and even the shape of the return value including the sensitive admin token. An agent has everything needed to call it correctly on the first attempt.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 83%, yet the description still adds meaning the schema cannot express: the precedence between `text` and `question`/`options`, the per-type option bounds (2-5 polls vs 2-12 rankings), and the rule that `question` alone yields a check-in. It also explains why `timezone` matters (local slot rendering and relative words like 'tomorrow'), not just its format.

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 the four resource types it can create (poll, check-in, availability board, ranking) plus the immediate outcome (a shareable link). This is unmistakably distinct from the sibling operations get/close/reopen/delete/respond_to_decision.

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

Usage Guidelines5/5

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

Explicitly lays out two invocation modes: the easy path (pass plain-language `text`, type inferred) with four concrete example strings, and the exact-control path (`question` + `options`). It also states the negative constraint that availability must be created from `text`, which prevents a predictable misuse.

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