Skip to main content
Glama

Discard an idea

flypost_discard_idea

Discard an idea the user does not want (the idea board's discard): it disappears from their ideas and is kept only as a signal so future brainstorms avoid it. Reversible in the app. Prefer this to deleting.

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": {
      "content_bank_item_id": "<content_bank_item_id>"
    },
    "name": "flypost_discard_idea"
  }
}

Input Schema

NameRequiredDescriptionDefault
content_bank_item_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Annotations only say destructiveHint=false and readOnlyHint=false; the description explains why the operation is non-destructive: the idea vanishes from the user's list but persists as a negative signal, and the action is reversible in the app. That is exactly the behavioral context an agent needs before performing a mutation on user data.

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 tight sentences that front-load the action and its effect, with the alternative rule last. The parenthetical '(the idea board's discard)' is slightly awkward but earns its place by mapping the tool to a UI affordance.

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?

For a single-parameter mutation with annotations and no output schema, the description covers effect, reversibility, and the delete alternative. It omits only parameter sourcing and error/not-found behavior, which are minor gaps at this complexity.

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 coverage is 0% and the description never mentions content_bank_item_id, where to obtain it, or what a content-bank item is. The parameter name is largely self-describing, so an agent can infer its meaning, but the description does not compensate for the documentation gap.

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 specific verb ('Discard') and resource ('an idea') and immediately clarifies the non-obvious semantic: the idea disappears from the user's board but is retained as a signal for future brainstorms. This distinguishes it sharply from a hard delete, and 'Prefer this to deleting' explicitly separates it from destructive siblings.

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?

Gives a clear trigger ('an idea the user does not want') and an explicit preference rule over deleting. It does not name a concrete alternative tool (e.g. a delete tool) or state exclusions such as when discarding is inappropriate, so it stops short of fully prescriptive guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.