stashcat-api-mcp

edit_poll_answer

Modify an existing poll answer option by updating its text, position, or selection limit. Provide the company and answer IDs for the specific option.

Instructions

Edits an existing answer option.

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>",
      "answer_id": "<answer_id>",
      "type": "<type>"
    },
    "name": "edit_poll_answer"
  }
}

Input Schema

Name	Required	Description
`type`	Yes	Answer type, e.g. "text"
`position`	No	Position/order
`answer_id`	Yes	Answer ID to edit
`company_id`	Yes	Company ID
`answer_text`	No	Answer text
`answer_limit`	No	Max selections for this answer

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.0Aug 10, 2026

TDQS

C2.8/5.0

Behavior2/5

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. 'Edits' implies mutation but gives no detail on side effects, reversibility, required fields, or response format. This is a significant gap for a mutation tool.

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

Conciseness3/5

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

The description is a single, short sentence that is not verbose, but it is under-specified. It provides only the basic function without any elaboration on usage or parameters, trading useful information for brevity.

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?

Given the tool has six parameters, three required, and no annotations or output schema, the description is far too brief. It fails to explain what fields are editable, how edits are applied, or what the result looks like, leaving the agent without enough context to invoke it correctly.

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?

Schema description coverage is 100%, meaning all parameters have descriptions in the schema. The tool description adds no extra semantic context beyond the schema, so it meets the baseline for high coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses a clear verb 'edits' and identifies the resource 'existing answer option', which distinguishes it from sibling tools like create_poll_answer and delete_poll_answer. However, it doesn't explicitly mention 'poll' in the description, relying on the tool name for context.

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?

The description provides no guidance on when to use this tool versus alternatives such as create_poll_answer or delete_poll_answer. It doesn't mention prerequisites like the answer already existing, nor any exclusions or recommended use cases.

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

Deploy Server