Skip to main content
Glama

List access requests

list_repo_capability_requests
Read-onlyIdempotent

List a connected repository's access requests, without secret values. Any workspace member; requires the repository environments feature. An open request carries remediation: a summary, a supplyCommand when a secret can satisfy the request, and a dismissCommand. Have the user run supplyCommand in their own terminal and enter the secret at the hidden prompt or on stdin (for example, piped from their secret manager). Never read the secret or pass it through the model, MCP, command arguments or flags. Tasks keep running without the secret; a saved secret is used from the next agent run. A dismissed request does not come back.

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>",
      "repo_id": "<repo_id>"
    },
    "name": "list_repo_capability_requests"
  }
}

Input Schema

NameRequiredDescriptionDefault
repo_idYesThe repository id from get_workspace.
workspace_idYesThe workspace id (from whoami).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Beyond the annotations (readOnly, idempotent, non-destructive), the description discloses the response shape of an open request (summary, supplyCommand, dismissCommand) and the stateful semantics: tasks keep running without the secret, a saved secret applies from the next agent run, and a dismissed request does not come back. The strong security directive about never reading or passing the secret is valuable operational context.

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?

The scope statement is front-loaded and the remediation workflow follows in a logical order. Every sentence carries information — capability, preconditions, remediation shape, the security rule, persistence, and dismissal permanence — though the security sentences are somewhat repetitive about not handling the secret.

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 two-parameter read tool with no output schema and full annotation coverage, this is nearly complete: it explains what an open request contains and the lifecycle of supply/dismiss. The only minor gap is that pagination or result-size behavior is not mentioned, which matters little for a repository-scoped list.

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 100%, with both workspace_id and repo_id documented in the schema itself (including provenance hints like 'from get_workspace' and 'from whoami'). The description adds no further meaning about the parameters, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'List a connected repository's access requests, without secret values.' An agent can tell this is the read-only listing counterpart to dismiss_repo_capability_request, approve_access_request and deny_access_request, though none of those siblings is named explicitly to sharpen the boundary.

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?

It states the access precondition ('Any workspace member') and a feature gate ('requires the repository environments feature'), which is useful context. However, it never says when to call this versus the dismissal or approval siblings — the reader must infer that this tool is the discovery step that surfaces the supplyCommand/dismissCommand the others act on.

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