Skip to main content
Glama

Visibility Genies

Restore an action

restore_action

Put a dismissed action back on the Actions board, in To do or Suggested. 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": "restore_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesThe action's id from list_actions.
statusNoWhere it goes back to: To do (todo) or Suggested.todo
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/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=false, so the description's main added value is the cost disclosure: "Uses no credits or provider calls." That is genuinely useful pre-call context an agent can weigh against credit-consuming siblings, though it doesn't cover behavior for an action that isn't dismissed (e.g., error vs. no-op).

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?

Two short sentences, front-loaded with the action and its destination state, followed by the cost note. No filler or redundant restatement of the tool name.

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 low-complexity mutation with full schema coverage, annotations and an output schema, the description covers what it does, where the item lands, and its cost profile. The only meaningful omission is what happens when the target action is not currently dismissed.

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%, with the status enum and projectId billing note both documented in the schema itself. The description's "To do or Suggested" phrasing merely restates the status enum, so it adds no meaning beyond structured fields.

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?

"Put a dismissed action back on the Actions board" names a specific verb and resource, and the mention of "To do or Suggested" pins the resulting states. It is unmistakably the inverse of dismiss_action and distinct from restore_project, so an agent can choose it without opening the schema.

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 the trigger condition (the action must be dismissed), but never says so explicitly and names no alternative for the non-dismissed case. There is no explicit exclusion or fallback guidance, leaving the agent to infer when this tool is the right call.

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