Skip to main content
Glama

Deny an access request

deny_access_request
Destructive

Deny a pending request for workspace access. Workspace owners only.

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": {
      "workspace_id": "<workspace_id>",
      "request_id": "<request_id>"
    },
    "name": "deny_access_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
request_idYes
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.3/5.0
Behavior3/5

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and non-idempotent, so the safety profile is covered structurally. The description adds the authorization constraint (owners only) and the state precondition (pending), but says nothing about whether the denial is reversible, whether the requester is notified, or what happens to the request record afterward.

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 short sentences, zero filler, with the action and scope stated before the authorization restriction. Nothing could be removed without losing information.

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

Completeness3/5

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

For a simple two-parameter destructive mutation with no output schema, the definition covers the action, the state precondition, and the authorization requirement. It still leaves the post-call effects and the sourcing of request_id unexplained, which matters for a destructive operation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 50%: workspace_id is documented ("from whoami") but request_id has no description anywhere. The description mentions no parameter at all, so it fails to compensate for the undocumented request_id or clarify how to obtain it.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ("Deny") plus resource ("a pending request for workspace access"), which clearly distinguishes it from the approve_access_request sibling without naming it. The only shortfall is that it never explicitly contrasts itself with approval or other request-handling tools.

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?

"Pending" and "Workspace owners only" give real preconditions, so an agent knows not to call it on already-resolved requests or as a non-owner. However, there is no explicit when-not guidance and no routing to alternatives such as approve_access_request or escalation paths.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources