AgentGate
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTGATE_URL | Yes | The URL of the AgentGate server | |
| AGENTGATE_API_KEY | Yes | The API key for authentication |
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| agentgate_requestC | Submit an approval request. Returns request ID and initial status. |
| agentgate_getB | Get the current status of an approval request by ID. |
| agentgate_listA | List approval requests with optional filters. |
| agentgate_decideA | Approve or deny a pending request. Use when you are the designated approver. |
| agentgate_list_policiesA | List all policies ordered by priority. |
| agentgate_create_policyC | Create a new policy with rules. |
| agentgate_update_policyC | Replace an existing policy (all fields required). |
| agentgate_delete_policyB | Delete a policy by ID. |
| agentgate_list_audit_logsB | List audit log entries with optional filters and pagination. |
| agentgate_get_audit_actorsB | Get unique actor values from audit logs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool targets a distinct operation: policy CRUD, request submission, decision, status retrieval, and auditing. No two tools overlap in purpose, making it clear which tool to use for each action.
All tools share the 'agentgate_' prefix and most follow a verb_noun pattern (e.g., create_policy, list_policies). However, 'decide' and 'request' lack an explicit object, and 'get' and 'list' are generic without the object in the name, causing slight inconsistency.
With 10 tools covering policy management, request handling, and auditing, the count is well-scoped for the domain. Each tool serves a clear purpose without redundancy.
The tool set provides full CRUD for policies, complete lifecycle for approval requests (submit, list, view, decide), and audit capabilities. No obvious gaps in the core approval workflow.