Skip to main content
Glama

WhichDateWorks

Create a group poll

create_poll

Make plans with friends, family, co-workers or any group: create a poll of candidate dates or times, and everyone marks which ones work for them, so the group can find a date or time that works for everyone. For example a dinner, a trip, game night, a team lunch, an offsite or a meeting. Use when the user is planning something with other people and hasn't settled on a date. Returns a link to share with the group and a private link for the organizer. Pass either dates (all-day options) or times (time slots with the user's timeZone), all in the future. Pass organizerName (the user's first name) when you know it. Give the user both links: inviteUrl to share with the group, and manageUrl, which only they should have.

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": {
      "title": "<title>"
    },
    "name": "create_poll"
  }
}

Input Schema

NameRequiredDescriptionDefault
datesNoAll-day options as YYYY-MM-DD calendar days. Use this or `times`, not both.
timesNoTime slot options. Use this or `dates`, not both.
titleYesWhat the event is, e.g. "Dinner with Sam and Alex".
durationNoDefault length of each time slot in minutes. Defaults to 60.
locationNoWhere it happens, as free text.
timeZoneNoIANA time zone the times are in, usually the user's, like "America/New_York". Required with `times` unless every time has an offset. Each participant sees the times in their own zone.
descriptionNoMore detail for the guests.
organizerNameNoThe user's first name, if you know it. The poll shows it as the host.

Output Schema

NameRequiredDescriptionDefault
titleYes
pollIdYes
optionsYes
timeZoneYes
inviteUrlYesShare this with the group. Anyone with it can vote.
manageUrlYesPrivate link for the user only: opens the poll to edit it, see results and pick the final date.
nextStepsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare openWorldHint=true, idempotentHint=false and destructiveHint=false, so safety is covered; the description adds real value on top by disclosing the two returned links, the privacy distinction between inviteUrl and manageUrl, and the future-only constraint on options. It doesn't mention limits such as the 1000-option cap or what happens with duplicate/invalid dates, which keeps it off a 5.

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 purpose, then usage trigger, then return values and parameter rules — a logical progression. The opening list of use cases ('friends, family, co-workers') and example events is somewhat padded and repeats the same idea twice, costing a point.

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?

Despite an output schema existing, the description usefully tells the agent which fields matter (inviteUrl for the group, manageUrl only for the organizer) and how to present them, which is action guidance the schema cannot convey. Combined with the parameter constraints, nothing needed to invoke this correctly is missing.

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?

With schema coverage at 100%, the baseline is 3; this description earns above that by restating the critical mutual exclusivity of dates and times, adding the 'all in the future' constraint that the schema does not encode, explaining timeZone's role with times, and telling the agent to supply organizerName. Much of it echoes existing schema text, so it isn't fully additive.

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 — 'create a poll of candidate dates or times' — plus the collaborative mechanism (everyone marks which work). The sibling get_poll_results is a retrieval tool, and this description's creation framing makes the distinction obvious without opening either schema.

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 an explicit trigger condition: 'Use when the user is planning something with other people and hasn't settled on a date,' reinforced by concrete examples (dinner, trip, game night, team lunch). It also states the dates-vs-times exclusivity. It stops short of naming when not to use it or pointing to get_poll_results for follow-up.

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