Skip to main content
Glama

Panel: turn an offer off

dismiss_offer

Permanently dismiss a results-panel offer type—web, profile, or anonymised_or_totals—so it no longer appears in the app.

Instructions

The user turned one kind of offer off for good in the results panel ("web", "profile" or "anonymised_or_totals"). App-only.

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": {
      "kind": "<kind>"
    },
    "name": "dismiss_offer"
  }
}

Input Schema

NameRequiredDescriptionDefault
kindYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations declare readOnlyHint=false and destructiveHint=false, so the agent already knows this mutates state without being classified as destructive. The description adds the genuinely useful fact that the dismissal is permanent ('for good'), which annotations do not convey. It does not say whether the change is reversible, what permission or panel context is required, or what the call returns.

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 short sentences, front-loaded with the effect and then the value set; nothing is padding. The past-tense opening and the bare 'App-only' tagline are terse to the point of ambiguity rather than wasteful.

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-destructive-per-annotation tool with no output schema, the description covers the action, the permanence, the allowed kinds, and the platform restriction. The remaining gap is the absence of any statement about the result or about the panel context the call must be made from.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0% and there is no enum constraint, so the description's inline enumeration of allowed values ('web', 'profile', 'anonymised_or_totals') is the only place the agent can learn valid inputs. This is real compensation for the schema gap. It does not explicitly tie the values to the 'kind' parameter name or note that it is required, which keeps it from a 5.

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 names a specific action and resource: turning off an offer 'for good' in the results panel, and enumerates the three offer types. That is enough to distinguish it from the many account/row/source siblings, which do entirely different things. It loses a point because the past-tense framing ('The user turned...') makes it read like a UI event record rather than an action the agent invokes.

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?

There is no explicit when-to-use or when-not-to-use guidance and no named alternative (e.g. how this differs from personal_offer). 'App-only' is a placement constraint, not usage guidance, and its meaning is left for the agent to infer.

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