Kaiku

ask_issue_question

Ask one person a question with pre-written answer options, in an issue's thread — the way to get a decision that does not get lost in the comment stream. The question appears as an ordinary comment (so every Jira-speaking reader sees it) and is tracked separately: the person you ask sees it counted in their Questions list until they answer. It does not wait for ever — give 'defaultOption' and the deadline takes it if nobody answers, so a blocked run can go on. Requires permission to comment in that project. NOTE: this is not the bgs 'ask_question' tool, which is the background-agent ledger — this one is a question to a person on a PM issue.

Input Schema

TableJSON Schema

Name	Required	Description
`to`	Yes	Who to ask: the username, which list_users hands you ready-made — never the display name. They must be able to see this project, and it cannot be you.
`key`	Yes	Issue key, e.g. 'UK-1'.
`options`	Yes	The answer options, in the order to offer them: at least 2, at most 8, each a short label rather than a paragraph. Fewer than two is not a question with options — that is a comment.
`question`	Yes	The question itself. Keep it to what the options answer.
`ttlHours`	No	How long to wait, in hours. Omitted is 48 (two days). 0 means no deadline at all — the question waits until somebody answers it, which is rarely what an agent wants.
`allowFreeText`	No	Whether the answerer may add words of their own beside the option they choose. Defaults to true. Set false when the answer has to be machine-comparable and nothing else.
`defaultOption`	No	Which option to take if nobody answers before the deadline, counted from 0. Give one whenever there is a safe assumption — it is what lets you carry on rather than stall. Omit it when no option is safe to assume: then the deadline only stops the waiting and decides nothing.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 22, 2026

TDQS

A4.5/5.0

Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses that the question appears as an ordinary comment, is tracked separately in the Questions list, has a deadline and default option behavior, and requires comment permission. This is comprehensive, though it doesn't cover error cases or response format.

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?

The description is detailed but every sentence contributes: purpose, behavior, deadline, permission, and differentiation. It's front-loaded with the primary function and has no filler. The note about the bgs tool is valuable for disambiguation.

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?

With 7 parameters, 4 required, and no output schema, the description covers the essential operational context: how the question appears, tracking, deadline semantics, default option, and permission. It's sufficient for an agent to invoke correctly.

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?

Schema coverage is 100%, so baseline is 3. The description adds context for defaultOption (safe assumption) and ttlHours (default 48 hours), which are not fully explicit in the schema, and clarifies the purpose of options. This adds meaningful value beyond the schema.

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 precisely the action (ask one person a question with pre-written options) and the resource (issue thread), and distinguishes it from the bgs ask_question tool. The verb and object are unambiguous, and it differentiates from sibling add_comment by emphasizing the tracked decision aspect.

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?

Explains the primary use case (getting a decision that doesn't get lost in the comment stream) and contrasts with the bgs tool. Provides guidance on when to use defaultOption and ttlHours. However, it doesn't explicitly name alternatives like add_comment for cases where options are not needed, though the distinction is clear.

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

All Kaiku 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?