Skip to main content
Glama
bruhsb
by bruhsb

paperclip_create_secret

Create a new encrypted secret for a company to store credentials or API keys. The value is encrypted and never returned, enabling secure agent references.

Instructions

⚠ Board-only: Create a new secret for a company. The value is stored encrypted and is never returned in any response.

Args:

  • companyId: string — Company UUID

  • name: string — Secret name (e.g. DATABASE_URL)

  • value: string — Secret value (stored encrypted, never returned)

  • provider: enum (optional) — Storage backend: local_encrypted | aws_secrets_manager | gcp_secret_manager | vault (default: local_encrypted)

  • description: string | null (optional) — Human-readable description

  • externalRef: string | null (optional) — External reference (e.g. ARN for AWS Secrets Manager)

Returns: Created secret metadata: id, companyId, name, provider, externalRef, latestVersion (starts at 1), description, createdByAgentId, createdByUserId, createdAt, updatedAt. Value is never returned.

Examples:

  • Use when: registering a new credential or API key that agents or routines will reference by name

  • Don't use when: the secret already exists and you want to update its value — use paperclip_rotate_secret instead

Error Handling:

  • 400: validation error → check that name and value are non-empty

  • 401: authentication failed → check PAPERCLIP_API_KEY

  • 403: permission denied → this tool requires a board (human-user) API key

  • 409: secret name already exists → use paperclip_rotate_secret to update its value

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
companyIdYesCompany UUID
nameYesSecret name (e.g. DATABASE_URL)
valueYesSecret value — stored encrypted, never returned in responses
providerNoStorage provider (default: local_encrypted)
descriptionNoHuman-readable description
externalRefNoExternal reference (e.g. ARN for AWS Secrets Manager)
Behavior5/5

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

Discloses board-only requirement, encryption, non-return of value, and error codes (400, 401, 403, 409). Annotations only provide destructiveHint=false and openWorldHint=false, so description adds essential context.

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?

Well-structured with sections (Args, Returns, Examples, Error Handling). Uses bullet points and emoji for caution. Every sentence is informative and no redundancy.

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

Completeness5/5

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

Covers all aspects: purpose, parameters, return shape (value never returned), usage guidance, error handling, and security considerations. No output schema, but description provides return fields.

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

Parameters4/5

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

Schema coverage is 100%, so baseline is 3. Description repeats schema info but adds context like default provider and meaning of externalRef (ARN). Also emphasizes value is never returned.

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 'Create a new secret for a company' with a specific verb and resource. It includes behavioral warnings (board-only, encrypted storage, value never returned) and distinguishes from the sibling tool paperclip_rotate_secret.

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

Usage Guidelines5/5

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

Explicit 'Use when' and 'Don't use when' sections with alternative tool (paperclip_rotate_secret) for updating existing secrets. Error handling also guides correct usage.

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/bruhsb/paperclip-mcp'

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