Skip to main content
Glama

Stop a suggestion

dismiss_suggestion
DestructiveIdempotent

Use this when the user says not to suggest something again: a status page, an alert channel, inviting a teammate, cron monitoring, subdomains or anomaly detection. Returns which suggestion is off. It stays off for this member in every assistant's conversations; the dashboard's own prompts are dismissed on the dashboard. Not for declining once: leaving a suggestion unanswered is enough.

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": {
      "suggestion": "<suggestion>"
    },
    "name": "dismiss_suggestion"
  }
}

Input Schema

NameRequiredDescriptionDefault
suggestionYesThe suggestion's key, as results give it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Adds real context beyond the annotations: the suppression is per-member, spans every assistant's conversations, and does not touch the dashboard's own prompts. With destructiveHint=true already declared, the remaining gap is that it never says whether/how the dismissal can be undone or re-enabled.

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?

Three tight sentences: trigger first, scope/return second, exclusion last. Every clause carries information; nothing is repeated from the schema or title.

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 one-parameter, non-open-world tool with no output schema, the description covers trigger, persistence scope, and return value. Only the reversibility/undo story is missing, which matters because the annotations flag it as destructive.

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 100% and the enum values are self-describing; the description's prose list ('a status page, an alert channel, inviting a teammate, cron monitoring, subdomains or anomaly detection') maps one-to-one onto the enum but adds no syntax, format, or sourcing 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.

Purpose4/5

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

The outcome is stated concretely ('Returns which suggestion is off', 'It stays off for this member'), so the effect of the tool is clear even though the verb is framed as a usage trigger rather than an action. It does not differentiate from the sibling dismiss_anomaly, and in fact lists 'anomaly detection' as one of the suggestions it dismisses, which blurs the boundary between the two tools.

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

Usage Guidelines5/5

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

Explicit trigger ('when the user says not to suggest something again'), explicit exclusion ('Not for declining once: leaving a suggestion unanswered is enough') with the alternative behavior named. An agent can decide without opening the schema.

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.

Resources