Skip to main content
Glama

Ask to change Guard

request_guard_edit

Ask an admin to let you read and change Guard settings (AI tool access, approvals, limits, access rules, groups and policies) for 12 hours. Call it when a Guard tool failed with GUARD_APPROVAL_REQUIRED and the user wants the change. Say in reason what you want to change. Show the user the approvalUrl from the result and wait until they say it is approved; calling again then returns the approval with state active. Asking again while a request waits returns the same request.

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

Input Schema

NameRequiredDescriptionDefault
reasonYesWhat you want to change and why, in one or two sentences the admin will read.

Output Schema

NameRequiredDescriptionDefault
messageNo
requestNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.9/5.0
Behavior5/5

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

Annotations only say it is a non-read-only, non-destructive, closed-world tool. The description goes well beyond that by explaining that the call does not itself grant access, that an admin must approve, that the grant lasts 12 hours, and that the call is idempotent while a request is pending. This is exactly the behavioral context an agent needs to avoid spamming requests.

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?

Roughly four sentences, each carrying distinct information: capability, trigger, required user-facing step, and retry/idempotency behavior. Nothing is repeated and the trigger is front-loaded after the capability statement.

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?

For a one-parameter approval-request tool with an output schema and annotations, this covers everything an agent needs: when to call, what to put in reason, how to present approvalUrl, and how repeated calls behave. Return-value detail is supplied by the output schema, so nothing material 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% and the single reason parameter is already documented with a length limit and audience. The description reinforces intent ('Say in reason what you want to change') and frames the audience as the admin, but adds no syntax or formatting detail beyond the schema, so it is an improvement rather than a large one.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ('Ask an admin to let you read and change Guard settings'), enumerates the affected scope (AI tool access, approvals, limits, access rules, groups, policies) and the duration (12 hours). An agent can distinguish this from get_guard or end_guard_edit without opening either schema.

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 an explicit trigger ('Call it when a Guard tool failed with GUARD_APPROVAL_REQUIRED and the user wants the change') plus the prerequisite of user consent, and spells out the follow-up loop: show the approvalUrl, wait for the user, call again to observe state active, and that a repeat call while pending returns the same request.

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