Skip to main content
Glama

Get access requests

get_access_requests
Read-onlyIdempotent

Read the access requests this token made with request_access; it never shows other tokens' requests. With request (an id), it returns that request's state: pending, active (approved and usable), denied, expired, used, ended or revoked. Pass wait (seconds) to hold the call until the user answers instead of asking them whether they did, and once it says active, retry the tool you needed. Without request, it lists up to limit requests, newest first, with state, project, scopes, reason and, while pending, the approveUrl to show the user: use it to find an id you lost or see what is still approved. To ask for new access use request_access. Read-only. No scope needed.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_access_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
waitNoWith request only: seconds to hold the call until the user approves or denies (0 to 270, default 0; 50 is safe everywhere)
limitNoWithout request only: requests to return, 1 to 100. Default 20.
requestNoA request id from request_access. With it: that request's state. Without it: every request this token made

Output Schema

NameRequiredDescriptionDefault
keysNoOnly while active
noteNoOnly when denied
untilNoOnly while active
scopesNoOnly while active
statusNo
requestNo
answerByNoOnly while pending
requestsNo
singleUseNoOnly while active
approveUrlNoOnly while pending
includesProtectedNoOnly while active

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds real behavior beyond them: the token-scoped visibility guarantee, the full state vocabulary (pending, active, denied, expired, used, ended, revoked), the blocking nature of wait, and that approveUrl appears only while pending. It also confirms no scope is needed.

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?

Information-dense and front-loaded, leading with scope and the two operating modes before state details. Some sentences are long and clause-chained, but essentially every sentence carries operational value with no filler.

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

Completeness5/5

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

An output schema exists, yet the description still summarizes the returned fields and the state machine, and it covers the blocking wait contract and the recommended follow-up action after 'active'. Nothing an agent needs to invoke or interpret this tool correctly is missing.

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 coverage is 100%, so the baseline is 3; the description still adds meaning, notably that results are ordered 'newest first' and that each entry carries state, project, scopes, reason, and pending-only approveUrl. It reinforces the request/no-request mode split in prose rather than merely restating types.

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 and resource plus a hard scope: it reads only the access requests this token created via request_access and 'never shows other tokens' requests'. It also explicitly routes new-access creation to request_access. It stops short of 5 because similarly named siblings (list_access_requests, check_access_request) go unmentioned, leaving some ambiguity unresolved.

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

Usage Guidelines5/5

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

Gives explicit when-to-use guidance for both modes: without request, 'use it to find an id you lost or see what is still approved'; with request, check state and 'once it says active, retry the tool you needed'. It also names the alternative for the adjacent need ('To ask for new access use request_access') and prescribes wait over polling the user.

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