Skip to main content
Glama

request_access

Ask the owner to approve a policy-gated API call or add an allowed host for a secret, then wait briefly for their decision. Use when a call is blocked by approval or host restrictions.

Instructions

Ask the owner to approve a request that policy gates behind approval (for example POST /v1/refunds), or to allow a host the secret is not yet locked to (pass upstream). Waits briefly for a decision. If the policy denies the path outright, the owner must change the policy; this tool will say so.

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": {
      "secret": "<secret>",
      "reason": "<reason>"
    },
    "name": "request_access"
  }
}

Input Schema

NameRequiredDescriptionDefault
scopeNo"METHOD /path" you want approved, e.g. "POST /v1/refunds"
reasonYes
secretYes
upstreamNoa host the call was refused for (host_not_allowed): https://host; approval adds it to the secret's allowed hosts

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/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 behavioral burden. It usefully discloses that the tool waits briefly for a decision and reports outright policy denial, but it does not explain approval persistence, rejection behavior, auth requirements, or the response shape.

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 description is compact and front-loads the primary action and examples. The sentences are purposeful, though the denial case could be integrated more tightly.

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 four-parameter tool with no annotations and no output schema, the description covers the main workflow but leaves important gaps. It does not explain the required secret and reason fields or describe the approval response in enough detail for an agent to interpret outcomes confidently.

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 only 50%, so the description should compensate more fully. It adds meaning for scope and upstream, including examples and the host_not_allowed case, but leaves the required secret and reason parameters largely unexplained.

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 states a specific action: asking the owner to approve a policy-gated request or to allow a host for a secret. It clearly distinguishes the two approval scenarios with examples, though it does not explicitly contrast itself with siblings such as call_api or explain_policy.

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

Usage Guidelines4/5

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

It gives clear when-to-use conditions: policy-gated approval and host_not_allowed situations. It also gives an important when-not condition: if policy denies the path outright, the owner must change the policy rather than using this tool. It does not name alternative tools for those cases.

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

Deploy Server

Other Tools