Skip to main content
Glama

Credential Manage Tool

credential_manage
Destructive

Manage encrypted credentials for external services. List, create, update, rotate, or delete API keys, OAuth tokens, and more without exposing secret data.

Instructions

Encrypted credential vault for external services (API keys, OAuth2 tokens, basic auth, bearer tokens). Secrets are encrypted at rest with the team's per-tenant key; secret_data is never returned by get — only metadata (name, type, expires_at, last_rotated_at).

Actions:

  • list (read) — optional: type, status filter.

  • get (read) — credential_id. Metadata only, secrets redacted.

  • create (write) — name, type (api_key/oauth2/basic_auth/bearer_token/custom), secret_data (object).

  • update (write) — credential_id + any creatable field.

  • delete (DESTRUCTIVE) — credential_id. Hard delete; not recoverable.

  • rotate (write) — credential_id, new_secret_data. Bumps last_rotated_at and re-encrypts.

  • oauth_initiate (write) — provider, scopes[]. Returns authorization URL.

  • oauth_finalize (write) — provider, code (from OAuth callback). Stores tokens, returns credential_id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYesAction to perform: list, get, create, update, delete, rotate, oauth_initiate, oauth_finalize
deadline_msNoOptional: max wall-clock time (ms) the tool may spend. If exceeded during the call, returns a DEADLINE_EXCEEDED error. Minimum 100 ms. Leave unset for no deadline.
statusNoFilter by status: active, disabled, pending_review
creator_sourceNoFilter by creator source: human, agent, system
limitNoMax results to return (default 10, max 100)
credential_idYesThe credential UUID
nameYesCredential name
typeYesCredential type: api_token, oauth2, basic_auth, ssh_key, custom_kv
secret_dataYesSecret data object (e.g. {"token": "..."} or {"username": "...", "password": "..."})
descriptionNoCredential description
expires_atNoExpiration date in ISO 8601 format (e.g. 2025-12-31T23:59:59Z)
agent_idNoUUID of the agent creating this credential. Sets creator_source=agent and status=pending_review until a human approves it.
service_nameYesHuman-readable name of the service being authorized (e.g. "GitHub", "Slack")
scopesNoList of OAuth scopes to request (e.g. ["read:user", "repo"])
credential_nameNoName to give the stored credential once OAuth completes
correlation_idYesThe correlation_id returned by credential_oauth_initiate
Behavior5/5

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

Beyond the destructiveHint annotation, the description details encryption at rest, that secret_data is never returned by get, hard delete irrecoverability, and OAuth workflow. This adds substantial behavioral context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively long with multiple paragraphs. While it front-loads the main purpose and uses bullet points for actions, some redundancy exists (e.g., repeating action types also in schema). Could be more concise.

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?

Covers actions and key behaviors but lacks return value descriptions for most actions (e.g., list, create). Since no output schema exists, this omission reduces completeness.

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 coverage is 100% with detailed parameter descriptions. The description lists actions with associated parameters but does not add new meaning beyond the schema, so baseline score applies.

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 tool as an 'Encrypted credential vault for external services' and lists all actions. This distinguishes it from sibling management tools which handle different resources.

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 provides clear context for credential management but does not explicitly exclude alternative tools or provide when-not-to-use guidance. Since no other credential tools exist, the context is sufficient.

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/escapeboy/agent-fleet-o'

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