Skip to main content
Glama

agoragentic_secret_store

Idempotent

Securely store encrypted secrets like API keys and passwords using AES 256 encryption in a vault for AI agents.

Instructions

Store an encrypted secret (API key, token, password) in your vault. AES 256 encrypted at rest. Costs $0.25 via the marketplace.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelYesLabel for the secret, for example 'openai_key' or 'stripe_token'
secretYesThe secret value to encrypt and store securely
hintNoOptional human readable hint to help you remember what this secret is for

Implementation Reference

  • Implementation of the AgoragenticSecretStore._run method which executes the secret storage request.
    def _run(self, label: str, secret: str, hint: Optional[str] = None) -> str:
        if not self.api_key:
            return json.dumps({"error": "API key required."})
        try:
            resp = requests.post(
                f"{AGORAGENTIC_BASE_URL}/api/vault/secrets",
                json={"input": {"label": label, "secret": secret, "hint": hint}},
                headers={
                    "Authorization": f"Bearer {self.api_key}",
                    "Content-Type": "application/json"
                },
                timeout=30
            )
            return json.dumps(resp.json(), indent=2)
        except Exception as e:
            return json.dumps({"error": str(e)})
  • Name registration of the AgoragenticSecretStore tool.
    name: str = "agoragentic_secret_store"
Behavior4/5

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

Annotations cover read/write status, idempotency, and safety, but the description adds valuable context: it discloses encryption details ('AES 256 encrypted at rest'), cost implications ('Costs $0.25 via the marketplace'), and hints at the tool's purpose for secure storage. No contradiction with annotations.

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?

The description is front-loaded with the core purpose, followed by encryption and cost details in two efficient sentences. Every sentence adds value without redundancy, making it appropriately sized and well-structured.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (a write operation with cost and encryption), annotations provide good behavioral coverage, and the schema fully describes inputs. The description adds encryption and cost context, but lacks output details (no output schema) and could mention idempotency or error handling more explicitly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all parameters. The description does not add any parameter-specific information beyond what the schema provides, such as format examples or constraints, meeting the baseline for high schema coverage.

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?

The description clearly states the specific action ('Store an encrypted secret'), resource ('in your vault'), and scope ('API key, token, password'), distinguishing it from sibling tools like 'agoragentic_secret_retrieve' and 'agoragentic_vault'. It provides concrete details about encryption and cost.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage context by specifying what types of secrets to store and mentioning the cost, but it does not explicitly state when to use this tool versus alternatives like 'agoragentic_secret_retrieve' or 'agoragentic_vault'. No exclusions or prerequisites are provided.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/rhein1/agoragentic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server