Skip to main content
Glama
Sign In

Genaya

by io.github.genaya-app
OverviewDiscussionsAdmin

Cancel a prepared change

cancel_action
DestructiveIdempotent

Drop one proposal the member declined or no longer wants: pass its action_id. A proposal still waiting (or a held send not yet out) is canceled and nothing runs; one that already ran answers its state - use undo_action for that. Free.

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": {
      "action_id": "<action_id>"
    },
    "name": "cancel_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
action_idYesThe action_id of the proposal to drop.

Output Schema

NameRequiredDescriptionDefault
statusYes
receiptYes
action_idYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real context beyond them: a still-waiting proposal or a held send is dropped and 'nothing runs', and an already-run action returns its state rather than being canceled. It also notes the call is free. It does not discuss auth/permission requirements, which keeps it below a 5.

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 dense sentences, front-loaded with the action and followed by the sibling routing and the no-op case. The trailing fragment 'Free.' is terse to the point of being cryptic, but it does convey cost information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists so return values need not be explained, and the description covers the one genuinely ambiguous case (an action that already ran). Nothing an agent needs to call this correctly is missing.

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 single action_id is documented in the schema, so the description only restates 'pass its action_id'. It adds the useful qualifier that the id refers to the proposal being dropped, but no format or sourcing detail beyond the schema.

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 resource ('Drop one proposal') and immediately names the sibling it is not ('use undo_action for that'), so an agent can distinguish cancel_action from undo_action without opening either schema.

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?

Gives both the selecting condition (a proposal the member declined or no longer wants) and an explicit exclusion with the alternative to use instead (already-ran actions go to undo_action). The routing decision is fully determined by the description.

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

All Genaya toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources