CrunchJunkie

decide_approval

Destructive

Approve or dismiss one item of the Approvals queue, as the Approve and Dismiss buttons on AI Visibility → Approvals do. Approve delivers it: an AI action plan or content brief is e-mailed to the automation's recipients (or the workspace owner); a report draft gets a share link (anyone with the link can then view that report) that is e-mailed to them; a manual task is marked done and nothing is sent. Dismiss closes the item and moves a drafted report to Deleted. Approving spends no AI and starts no scan. It acts on an explicit decision, shows a preview of who gets what, and applies only with confirm:true. Requires MCP write actions.

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": {
      "approvalId": "<approvalId>",
      "decision": "<decision>"
    },
    "name": "decide_approval"
  }
}

Input Schema

Name	Required	Description
`confirm`	No	Set true to apply. Omit for a preview. With confirm:true, also pass the preview's previewToken.
`decision`	Yes	approve (deliver it) or dismiss (close it without sending).
`approvalId`	Yes	The item (id from list_pending_approvals).
`previewToken`	No	With confirm:true: the previewToken from this tool's preview (valid 15 minutes, once, for exactly the previewed arguments).

Schema Changelog

Changes observed during successful MCP inspections.

Changed2 schema fields changedOct 24, 2026

changedInput schema / $schema

Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"

removedInput schema / additionalProperties
```
Removed value: -false
```

First observedOct 19, 2026

TDQS

A4.7/5.0

Behavior5/5

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

The description goes well beyond the annotations by disclosing exactly what happens for each item type: e-mails to recipients or the workspace owner, a public share link for report drafts, manual tasks marked done with nothing sent, and dismiss moving report drafts to Deleted. It also states that approval spends no AI and starts no scan, and it explains the preview and confirm:true safeguard.

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?

The description is front-loaded with the core action and then earns its length by explaining the materially different outcomes of approve and dismiss. Given the destructive write and the need to understand delivery side effects, the length is justified and there is no filler.

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?

For a destructive, write-capable tool with no output schema, the description covers the important behavioral details: what is delivered or destroyed, who receives notifications, the public-link implication, preview behavior, and the confirm requirement. It is complete enough for an agent to invoke it correctly.

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 100%, so the schema already documents all four parameters. The description still adds meaningful semantic context by explaining what approve versus dismiss actually does for different item types and by describing the preview/confirm flow, which helps the agent understand the effect of the decision parameter.

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?

The description gives a specific verb and resource — approve or dismiss one item in the Approvals queue — and distinguishes the two actions clearly. It also anchors the tool to the equivalent UI buttons, so an agent can immediately tell what it does versus list_pending_approvals.

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?

It clearly explains the contexts for approving versus dismissing by spelling out the consequences of each decision. It also establishes the preview-and-confirm workflow, but it does not explicitly name alternatives or say when not to use this tool versus related tools such as resolve_signal.

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

All CrunchJunkie tools Inspect

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

Need Help?