Skip to main content
Glama

Stop changing Guard

end_guard_edit
Idempotent

Give back your approval to change Guard settings as soon as the changes the user asked for are done, instead of keeping it for the full 12 hours. Also withdraws a request still waiting. Guard is then closed to you again until an admin approves a new request.

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": "end_guard_edit"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
endedNoHow many approvals or requests were ended.
messageNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare this is a non-read-only, idempotent, non-destructive operation. The description adds real state-transition context beyond that: the approval window is 12 hours by default, the guard closes again afterward, and re-entry requires a fresh admin approval. It doesn't address authorization requirements for the call itself, so not a 5.

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 primary action is front-loaded in the first sentence, with the secondary withdraw case and the consequence following. Three sentences, each carrying information, though the conversational phrasing ('Give back your approval') could be tighter.

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?

With zero parameters and an output schema present, the description only needs to convey purpose, both use cases, and consequences, and it does all three. An agent has everything needed to decide to call it.

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?

The tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline 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 states a specific action on a specific resource: releasing the caller's approval to change Guard settings, plus withdrawing a pending request. It is clearly the counterpart of request_guard_edit (implied by 'instead of keeping it for the full 12 hours'), though it never names that sibling outright, which keeps it from a 5.

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 triggering conditions: call it as soon as the user's requested changes are done rather than sitting on the 12-hour window, and it covers a second case, withdrawing a request still waiting. It lacks an explicit named alternative or a 'do not use when' exclusion, so it falls short of a 5.

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