agent-keys
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| list_servicesA | List all supported services with their status (whether a key is stored), category, description, and signup URL. |
| get_api_keyA | Get a stored API key for a service. Returns the key if stored, or provisioning guidance if not. |
| store_api_keyB | Store an API key in the encrypted vault. |
| check_api_keyA | Verify a stored API key still works by hitting the service's test endpoint. |
| provision_api_keyB | Get step-by-step instructions and direct signup URL for acquiring an API key for a service. |
| remove_api_keyB | Remove an API key from the vault. |
| export_envA | Export stored API keys as shell export statements (e.g. export OPENAI_API_KEY=...). |
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 7 tools
Each tool has a clearly distinct purpose: listing services, getting/storing/checking/provisioning/removing keys, and exporting. No overlap.
All tool names follow a consistent verb_noun pattern (e.g., list_services, get_api_key, store_api_key). The use of 'env' in export_env is a different noun but still fits the pattern.
7 tools is well-scoped for managing API keys, covering all essential operations without being excessive or insufficient.
The tool surface covers the full lifecycle: discovery, storage, retrieval, verification, provisioning guidance, deletion, and export. No obvious gaps.