Skip to main content
Glama

agoragentic_secret_retrieve

Read-onlyIdempotent

Retrieve decrypted secrets from your vault to access stored credentials securely. Free access to your own stored secrets.

Instructions

Retrieve a decrypted secret from your vault. Free, no cost to access your own credentials.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
labelNoLabel of the secret to retrieve. Omit to list all stored secrets.

Implementation Reference

  • The handler class for the `agoragentic_secret_retrieve` tool, which retrieves decrypted secrets from the Agoragentic vault.
    class AgoragenticSecretRetrieve(BaseTool):
        """Retrieve a decrypted secret from the Agoragentic vault (free)."""
    
        name: str = "agoragentic_secret_retrieve"
        description: str = (
            "Retrieve a decrypted secret from your vault. FREE. "
            "Provide a label to decrypt a specific secret, or omit to list all labels."
        )
        args_schema: Type[BaseModel] = SecretRetrieveInput
        api_key: str = ""
    
        def _run(self, label: Optional[str] = None) -> str:
            if not self.api_key:
                return json.dumps({"error": "API key required."})
            try:
                params = {}
                if label:
                    params["label"] = label
    
                resp = requests.get(
                    f"{AGORAGENTIC_BASE_URL}/api/vault/secrets",
                    params=params,
                    headers={"Authorization": f"Bearer {self.api_key}"},
                    timeout=15
                )
                data = resp.json()
                return json.dumps(data.get("output", data), indent=2)
            except Exception as e:
                return json.dumps({"error": str(e)})
  • Input schema for the `agoragentic_secret_retrieve` tool.
    class SecretRetrieveInput(BaseModel):
        label: Optional[str] = Field(default=None, description="Label of the secret to retrieve (omit to list all)")
Behavior3/5

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

Annotations already provide key behavioral hints (readOnlyHint: true, idempotentHint: true, destructiveHint: false, openWorldHint: true). The description adds some context by stating 'free, no cost to access your own credentials', which hints at cost and ownership aspects not covered by annotations. However, it lacks details on rate limits, authentication needs, or what 'openWorldHint' implies in practice.

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 highly concise with two brief sentences that directly state the tool's function and a key benefit ('free, no cost'). There is no redundant or unnecessary information, making it front-loaded and efficient for an AI agent to parse quickly.

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

Completeness3/5

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

Given the tool's low complexity (1 optional parameter, no output schema) and rich annotations, the description is somewhat complete but has gaps. It covers the basic purpose and cost aspect, but lacks details on return values, error handling, or how 'openWorldHint' affects usage. With annotations handling safety and idempotency, the description is adequate but not fully comprehensive.

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%, with the parameter 'label' well-documented in the schema. The description doesn't add any parameter-specific semantics beyond what the schema provides, such as format examples or constraints. Since schema coverage is high, the baseline score of 3 is appropriate, as the description doesn't compensate but also doesn't need to.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb 'retrieve' and resource 'decrypted secret from your vault', making the purpose evident. It distinguishes from sibling 'agoragentic_secret_store' by focusing on retrieval rather than storage. However, it doesn't explicitly differentiate from other potential read operations like 'agoragentic_memory_read' or 'agoragentic_search'.

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

Usage Guidelines2/5

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

The description provides minimal usage guidance, mentioning it's 'free' and for accessing 'your own credentials', but offers no explicit when-to-use rules, alternatives, or exclusions. It doesn't clarify when to use this versus other read tools like 'agoragentic_search' or 'agoragentic_memory_read', leaving the agent with little direction.

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