Skip to main content
Glama

wait_for_access

Blocks until a person approves or denies a pending access request, polling for up to 100 seconds and returning the answer. Use it after requesting access to get the decision.

Instructions

Wait for the person's answer to a request_access that is still pending (up to 100 seconds).

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

Input Schema

NameRequiredDescriptionDefault
request_idYesThe request_id request_access returned.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose the one critical trait: the call blocks for up to 100 seconds. However it does not say what the agent gets back on approval, denial, or timeout, nor whether the wait is interruptible or idempotent, which matters for a long-blocking call.

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?

A single sentence with no waste; the dependency on request_access and the 100-second ceiling are both front-loaded and immediately actionable.

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 blocking tool with no annotations and no output schema, the description should state the possible outcomes (approved/denied/timed out) so the agent can branch correctly. The timeout is covered but the result semantics are left entirely unstated.

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?

Only one parameter with 100% schema coverage, so the schema already documents request_id. The description reinforces its origin ('the person's answer to a request_access') but adds no format or lifecycle detail beyond that baseline.

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?

Names a specific verb (wait) and the exact resource (the person's answer to a pending request_access), plus a bounded duration. It is clearly distinguishable from the sibling request_access because it operates on an already-issued request rather than creating one.

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 only implied: 'still pending' plus the schema note that request_id comes from request_access tells the agent when to call it. There is no explicit guidance on what to do if the request was already answered, what happens on timeout, or whether re-calling is appropriate.

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