Skip to main content
Glama
Sign In
NitroWatch

NitroWatch

by Mohith535
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

deny_action

Deny a pending approval to block execution, with the denial and reason stored permanently in the audit trail.

Instructions

Human denies a pending action. Nothing executes, and the denial is recorded permanently against that tool.

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

Input Schema

NameRequiredDescriptionDefault
reasonNoWhy it was denied — stored in the audit trail
approvalIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

With no annotations, the description carries the burden. It discloses two key behaviors: 'Nothing executes' and 'denial is recorded permanently,' which is valuable context. However, it does not state what happens to the pending action after denial.

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 concise sentences, front-loaded with the primary action, and no filler. Every word earns its place.

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 simple tool, the description covers the core behavior and primary side effect (permanent recording). It lacks mention of return values and the fate of the pending action, but these are not critical given the tool's simplicity.

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 50% (reason has a description, approvalId does not). The description adds context that approvalId refers to the pending action, but not explicitly. It partially compensates for the gap but could be clearer.

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 uses a specific verb and resource: 'Human denies a pending action.' This clearly distinguishes it from siblings like approve_action and 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 Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied (deny a pending action) but there is no explicit mention of when to use this versus approve_action or any exclusions. No alternatives are named.

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