Skip to main content
Glama

Get Guard settings

get_guard
Read-only

Read Guard for the whole workspace: every connection with its AI tool access, approval mode and AI limits, the workspace's members, the groups used by access rules, and the policies. Call it before changing Guard so you change the right thing. Needs an active Guard approval; see request_guard_edit.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already mark this as read-only and closed-world, and the description adds real context beyond them: it requires an active Guard approval to succeed and defers to request_guard_edit. It does not say what happens on failure (error shape, whether partial data returns), which keeps it short of 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three short sentences, front-loaded with what is returned, followed by the usage rule and the prerequisite. No filler or repetition of the annotations.

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 no output schema, the description carries the return-value burden and does so by enumerating the five data groups the caller gets back. Combined with the approval prerequisite, an agent has everything needed to call it correctly.

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 no parameters (schema is an empty object), so there is nothing for the description to disambiguate; baseline is 4. It correctly avoids inventing parameter-like filtering options.

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 ("Read Guard") and immediately enumerates the scope: connections with AI tool access, approval mode and AI limits, members, groups, and policies. The whole-workspace framing distinguishes it from the granular list_* siblings without needing to name them.

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 when-to-use rule ("Call it before changing Guard so you change the right thing") plus the gating condition ("Needs an active Guard approval") and routes the agent to the named alternative request_guard_edit when approval is missing. Both the timing and the prerequisite are spelled out.

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