stashcat-api-mcp

create_poll_question

Add a question to an existing poll by providing the poll ID, question text, and question type. Optionally set position and answer limit for order and selection constraints.

Instructions

Creates a question within a poll.

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": {
      "company_id": "<company_id>",
      "poll_id": "<poll_id>",
      "name": "<name>",
      "type": "<type>"
    },
    "name": "create_poll_question"
  }
}

Input Schema

Name	Required	Description
`name`	Yes	Question text
`type`	Yes	Question type, e.g. "text"
`poll_id`	Yes	Poll ID
`position`	No	Position/order of the question
`company_id`	Yes	Company ID
`answer_limit`	No	Max answers a user can select

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

B3.2/5.0

Behavior2/5

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that it creates a question, without mentioning side effects, permission requirements, idempotency, or validation behavior, leaving significant gaps.

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 a single, concise sentence with no redundant information. It is front-loaded and appropriately sized for a simple create operation.

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

Completeness2/5

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

For a mutation tool with no annotations and no output schema, this description is too minimal. It fails to explain what the tool returns, any constraints on the poll's state, or how it fits into the larger poll lifecycle, leaving the agent without sufficient context.

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?

The schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds no additional semantic detail beyond what the schema already provides.

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?

The description clearly states that the tool creates a question within a poll, using a specific verb and resource. This distinguishes it from sibling tools like edit_poll_question and delete_poll_question.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives. It doesn't mention prerequisites such as requiring an existing poll to exist, nor does it exclude cases where this tool should not be used (e.g., editing or deleting questions).

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

Deploy Server