Agent Keyring
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOGLEVEL | No | Log level for the server. Use DEBUG for more detail, ERROR for quiet mode. | WARNING |
| KEYRING_GCP_PREFIX | No | Prefix added to secret names when stored in GCP Secret Manager. | |
| KEYRING_GCP_PROJECT | No | The GCP project ID. When set, uses GCP Secret Manager instead of the local file store. | |
| KEYRING_SECRETS_ROOT | No | Root directory for resolving PASTE_FROM references. | 3 dirs up |
| KEYRING_SECRET_STORE | No | Path to the local secrets file. | .secrets.json |
| KEYRING_GCP_CACHE_TTL | No | Cache TTL for GCP secret values. Use 0 to disable caching. | |
| GOOGLE_APPLICATION_CREDENTIALS | No | Path to a GCP service account key file 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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| keyring_list_availableA | List secrets the calling agent can access. Returns names and descriptions only — never values. Args: did: Agent's DID (did:key:...) for identity verification. agentmail_inbox: Agent's AgentMail address (e.g. sofer@agentmail.to) as fallback identity. |
| keyring_authenticated_requestA | Make an authenticated API call using a managed secret. The key never appears in the response. The keyring retrieves the secret, makes the API call, and returns only the response data. Every call is logged to the checkout ledger. Args: service: Service identifier (e.g. 'agentmail', 'stripe', 'ga4', 'firebase'). For unregistered services, pass any name — the generic adapter handles the request if base_url is in params. secret_name: Name of the secret to use (from keyring_list_available). method: HTTP method (GET, POST, PUT, DELETE). endpoint: API endpoint path (appended to service base URL). params: Query parameters for the request. For unregistered services, include: base_url (required), auth_type ('bearer'|'header'|'basic'|'query', default 'bearer'), auth_header (header name when auth_type='header'). body: JSON body for POST/PUT requests. scope: Optional scope for multi-value keys (e.g. 'fleet', 'mcp'). When set, tries secret_name:scope first, falls back to secret_name. purpose: Why this request is being made (logged to ledger). did: Agent's DID for identity verification. agentmail_token: AgentMail API key for identity fallback. agentmail_inbox: Agent's AgentMail address for identity fallback. |
| keyring_checkout_historyB | Query the checkout ledger — who accessed what, when, and why. Args: agent_id: Filter by agent (DID or AM address). service: Filter by service name. secret_name: Filter by secret name. days: How far back to look (default 30). |
| keyring_agent_affinityA | Analyze agent-service affinity patterns from the checkout ledger. Returns which agents use which services most — the raw data for workstation specialization analysis and context overload detection. Args: days: How far back to analyze (default 30). |
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 4 tools
Each tool has a clearly distinct role: listing available secrets, making an authenticated request, querying the audit ledger, and analyzing ledger patterns. The closest pair, checkout_history and agent_affinity, are separated by raw logging versus aggregate analysis.
The shared keyring_ prefix provides some consistency, but the suffixes are grammatically mixed: list_available is verb-like, while authenticated_request, checkout_history, and agent_affinity are noun phrases. A consistent verb_noun pattern would make the tool names more predictable.
Four tools is well-scoped for an agent-facing keyring: discovery, usage, audit, and analytics. Each tool serves a distinct purpose without redundancy or unnecessary bloat.
The surface covers the full agent-facing workflow: see what secrets are available, use them without exposing values, review the audit trail, and analyze usage patterns. Secret lifecycle management tools are absent but appear intentionally reserved for administrators rather than agents.