Skip to main content
Glama

Approve an access request

approve_access_request

Grant member or admin access to a requester. 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>",
      "role": "<role>"
    },
    "name": "approve_access_request"
  }
}

Input Schema

NameRequiredDescriptionDefault
roleYes
request_idYes
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, so mutation semantics and non-idempotency are covered structurally. The description adds genuinely new behavioral context with the owner-only authorization requirement, but says nothing about what approval does as a side effect (notifying the requester, consuming/closing the request, or whether it can be undone).

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short sentences, front-loaded with the action and ending with the access constraint. Nothing is wasted, though the fragmentary final sentence could be phrased as a complete prerequisite clause for smoother reading.

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 three-required-parameter mutation with no output schema and thin schema coverage, the description leaves material gaps: no return/confirmation behavior, no downstream effects, and no failure conditions (e.g., request already resolved, caller not an owner). It covers who may call it and what role is granted, which is the core, but not enough for full confidence.

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?

With schema coverage at 33%, the description partially compensates by explaining that role takes member or admin and that the target is a requester. The request_id and workspace_id parameters get no added meaning in the description; workspace_id is only documented via the schema.

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?

The description names a specific action and resource ('Grant member or admin access to a requester') and specifies the role scope from the enum. It is clearly a write operation on an access request, but it does not explicitly contrast itself with the obvious inverse sibling deny_access_request, leaving that differentiation to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

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

'Workspace owners only' functions as a permission prerequisite rather than usage guidance. There is no statement of when to choose this over deny_access_request, invite_member, or set_member_role, and no mention of prerequisites such as a pending request existing.

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