Skip to main content
Glama
Guardian by Odingard

Guardian by Odingard

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
GUARDIAN_BASE_URLYesThe Guardian API base URL.
GUARDIAN_ADAPTER_IDNoOptional override for the tool adapter ID.
GUARDIAN_AUTO_REGISTERNoSet to true to enable automatic tool registration in the proxy. Disabled by default.
GUARDIAN_CONNECTION_IDYesThe Guardian connection ID, for example a value beginning with pcn_.
GUARDIAN_AGENT_CREDENTIALYesThe Guardian agent credential, for example a value beginning with gak_.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
guardian_invoke_toolA

Run a tool registered on a Guardian connection, instead of calling it directly. Guardian's rules decide ALLOW, ASK or DENY before anything runs. ALLOW runs the tool at once (it can change the target system) and returns the decision, requestId and execution record. ASK runs nothing and returns a requestId: wait for the person to approve it in Guardian, then call guardian_claim. DENY, or Guardian unreachable (reasonCode SERVICE_UNAVAILABLE), runs nothing; each call is a new request, so after an unknown outcome check guardian_record before calling again.

guardian_claimA

Run a request that guardian_invoke_tool held as ASK, once the person has approved it in Guardian. Guardian issues the capability and runs the approved call with its original arguments (it can change the target system), then returns ALLOW with the execution record. Before approval it returns ASK again and runs nothing; a denied, expired or unknown requestId returns DENY with a reasonCode; Guardian unreachable fails closed (SERVICE_UNAVAILABLE) and can be retried. An approval is used once: claiming the same requestId again does not run the call a second time.

guardian_recordA

Look up the evidence records Guardian holds for one request, to see what was decided and whether the call ran. It changes nothing and runs no tool, so calling it again is safe. Returns the requestId and its list of records; an unknown requestId, or Guardian unreachable, returns ok: false with a reasonCode. Use it after an unknown or unclear outcome, before trying a call again.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 3 tools

Disambiguation4/5

Each tool has a distinct role: guardian_invoke_tool is the entry point for governed calls, guardian_claim executes an already-approved ASK request, and guardian_record is a read-only audit lookup. The claim/invoke boundary is slightly subtle because both can run a tool, but the descriptions clearly distinguish initiation from approval execution.

Naming Consistency5/5

All tools use the guardian_ prefix and snake_case, with predictable verb-oriented names (claim, invoke_tool, record). The convention is consistent throughout and easy to scan.

Tool Count5/5

Three tools are well matched to a narrowly scoped governance/approval wrapper: one to invoke, one to claim an approval, and one to inspect records. No tool feels redundant or missing for this purpose.

Completeness4/5

The surface covers the key decision lifecycle: invoke, defer to approval, claim after approval, and inspect evidence afterward. A minor gap is the lack of an explicit pending-request listing, though the external Guardian UI plausibly handles that workflow.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues