OohWeGo

Ask the group

ask_poll

Asks everyone on the trip a question with 2 to 8 options, each a wishlist pin not yet planned (its id, from get_wishlist) or text. Use it when the group has to choose, rather than choosing for them.

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": {
      "question": "<question>",
      "options": "<options>",
      "tripId": "<tripId>"
    },
    "name": "ask_poll"
  }
}

Input Schema

Name	Required	Description
`tripId`	Yes	The trip’s id, from list_trips
`options`	Yes
`closesAt`	No	When it closes by itself; never if not given
`multiple`	No	People pick several options; one if not given
`question`	Yes

Output Schema

Name	Required	Description	Default
`poll`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

AddedNov 4, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=false. The description adds relevant context beyond that, namely that the poll is broadcast to everyone on the trip and that options may be unplanned wishlist pins sourced from get_wishlist. It does not cover notification behavior or what happens when a poll closes, which are minor gaps.

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?

Two sentences, front-loaded with the action and the constraint, then the usage rule. The parenthetical is dense but informative; no wasted words.

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?

An output schema exists, so return values need not be described; annotations cover the safety profile. What remains is a mutation/broadcast tool whose key constraints (option source, count) are stated, though the effect of closesAt and multiple is left implicit.

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?

With 60% schema coverage, the description partly fills the gap by explaining option semantics (wishlist pin id or free text, sourced from get_wishlist) and the option count range. It says nothing about closesAt or multiple, leaving those to the schema descriptions. Adequate but not compensating fully.

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 concrete action (ask everyone on the trip a question) plus the option constraint (2–8 options, each a wishlist pin not yet planned or text). An agent can distinguish 'ask' from 'answer_poll' without consulting the 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?

Explicit when-to-use guidance: 'Use it when the group has to choose, rather than choosing for them.' That gives a clear selection rule against sibling actions like add_activity or suggest_idea, though it stops short of naming those alternatives.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All OohWeGo tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?