Skip to main content
Glama
Sign In
dashclaw

dashclaw

by ucsandman
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Approve action

approve_action

Approve a pending action request to unblock a matching rerun. Rerun the original action afterwards to execute the approved operation.

Instructions

Approve a pending action request for one matching rerun. This never executes the provider call by itself; rerun the original action after approval.

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": "approve_action"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional human review note
approvalIdYesApproval id returned by an approval_required response

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavioral traits. It clarifies that the tool never executes the provider call, which is a key behavioral note. However, it does not mention any potential side effects, permissions required, or safety characteristics like destructiveness. More transparency would be beneficial.

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?

Extremely concise with two sentences. Every word adds value, and the critical behavioral note is front-loaded. No redundant information.

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?

Given no output schema and no annotations, the description covers the main purpose, workflow, and key behavioral constraint. It could mention what the tool returns (e.g., success confirmation), but the lack is compensated by the clear focus on action.

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 description coverage is 100%, but the description adds context: it explains that 'approvalId' comes from an 'approval_required response' and that 'note' is optional. This goes beyond the schema descriptions, providing valuable operational context.

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?

Clearly states the verb 'Approve' and the resource 'pending action request'. Specifies it is for 'one matching rerun', distinguishing it from sibling 'reject_action' and implied approval-related tools.

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 states that the tool does not execute the provider call and that the original action must be rerun after approval. This guides the agent on the correct workflow. However, it does not explicitly mention when not to use it, though the context of pending approvals is clear.

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