Skip to main content
Glama
Sign In
stashcat-api-mcp

stashcat-api-mcp

by dclausen01
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

delete_poll_answer

Remove an answer option from a poll question by providing the company ID and answer ID.

Instructions

Deletes an answer option from a question.

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>"
    },
    "name": "delete_poll_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
answer_idYesAnswer ID to delete
company_idYesCompany ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior2/5

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

No annotations are provided, so the description must disclose behavioral traits. It only says 'deletes' without mentioning whether the deletion is permanent, affects existing votes, requires permissions, or has other consequences. For a destructive action, this is a significant gap.

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 one short, active sentence with no wasteful words. It is front-loaded with the verb 'deletes' and immediately states the resource, making it highly concise and structured.

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

Completeness3/5

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

The tool is simple with well-documented parameters and no output schema, so the description covers the basic operation. However, it omits important context such as irreversibility and side effects, which is particularly relevant for a delete action without annotations.

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 input schema fully describes both parameters ('Answer ID to delete' and 'Company ID'), achieving 100% coverage. The description adds no additional parameter meaning, so the baseline of 3 applies.

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 uses a specific verb 'deletes' and clearly identifies the resource as 'an answer option from a question.' This distinguishes it from sibling tools such as delete_poll_question and vote_poll.

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

Usage Guidelines3/5

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

The description implies usage when an answer option needs to be removed from a question, but it provides no explicit guidance on when to prefer this tool over alternatives or any exclusions. The purpose is clear, but context for selection is minimal.

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

Deploy Server

Other Tools