Skip to main content
Glama
Sign In
dashclaw

dashclaw

by ucsandman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Reject action

reject_action

Reject a pending approval request to prevent its later execution. Provide the approval ID and optional note to block the action permanently.

Instructions

Reject a pending action request so it cannot be approved later.

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>"
    },
    "name": "reject_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional rejection note
approvalIdYesApproval id returned by an approval_required response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior3/5

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

With no annotations, description indicates a mutation (rejection) but lacks details on permissions, reversibility, or side effects. Adequate but minimal.

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?

Single sentence, front-loaded with action and effect, no wasted words.

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?

Covers essential purpose for a simple tool; could mention return behavior or confirmation, but adequate given context.

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 description adds no extra meaning. Baseline score of 3 applies.

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?

Description clearly states the verb 'reject' and the resource 'pending action request' with the effect 'cannot be approved later', distinguishing it from sibling tool 'approve_action'.

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?

Implies use for rejecting pending actions but does not explicitly state when not to use or provide alternatives beyond the sibling name.

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

Deploy Server

Other Tools