Skip to main content
Glama

Visibility Genies

Dismiss an action

dismiss_action
Destructive

Move a saved action to Dismissed. Nothing is deleted: restore_action puts it back. A dismissed audit finding returns only if more pages are affected or it gets worse; other actions stay dismissed until restored. Uses no credits or provider calls.

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": {
      "projectId": "<projectId>",
      "id": "<id>"
    },
    "name": "dismiss_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe action's id from list_actions.
projectIdYesRequired. The Visibility Genies project this call works in and is billed to. Call list_projects to find one.

Output Schema

NameRequiredDescriptionDefault
metaNo
actionYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Goes well beyond the annotations: it clarifies that despite destructiveHint=true nothing is actually deleted, pins down the reversibility mechanism, explains the conditional re-raise behavior specific to audit findings, and discloses cost ('no credits or provider calls'). That cost/reversibility context is exactly what annotations cannot convey.

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 short sentences, front-loaded with the state change, then reversibility, then edge-case semantics and cost. No filler or restatement of the 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 two-parameter state-change tool with a full schema, an output schema, and rich annotations, the description covers operation, reversibility, edge-case behavior, and cost. Only the absence of guidance on who may dismiss or how it relates to other lifecycle tools keeps it short of complete.

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%, so both projectId and id are already documented in the schema, including that id comes from list_actions and that projectId is billed. The description adds no parameter-level meaning of its own, which makes the baseline 3 appropriate.

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 and state transition ('Move a saved action to Dismissed') on a named resource, and immediately names the inverse tool restore_action, so an agent can separate it from move_action, edit_action, or update_action without opening a schema.

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?

Explicitly gives the undo path (restore_action) and the condition governing persistence ('a dismissed audit finding returns only if more pages are affected or it gets worse'), which tells the agent what dismissal means downstream. It stops short of saying when to dismiss versus use another lifecycle tool such as move_action or archive, so there is a small residual gap.

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