Skip to main content
Glama
privacyplaybook

sops-mcp

by privacyplaybook
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

sops_create_oidc_secret

Create an Authelia-compatible OIDC client secret: generates a 64-char secret plus its PBKDF2-SHA512 hash in one encrypted file, returning the hash for Authelia's config.

Instructions

Convenience tool: create an Authelia-compatible OIDC client secret. Generates KEY_NAME as a 64-char alphanumeric 'generated' secret AND KEY_NAME_HASH as a 'derived' PBKDF2-SHA512 hash of it, stored together in a new encrypted file. The hash is returned in the response for pasting into Authelia's configuration.yml. Equivalent to calling sops_create_secrets with one generated and one derived (pbkdf2_sha512_authelia) entry.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
domainNoName of the key domain to encrypt to / decrypt with. Optional. Defaults to the domain recorded in the file's _meta_unencrypted block, and failing that to 'default'. Call sops_list_domains to see what this server has configured.
key_nameYesBase name for the plaintext secret (e.g. GRAFANA_OIDC_CLIENT_SECRET). The hash will be stored as KEY_NAME_HASH. Must match ^[A-Z][A-Z0-9_]*$.
descriptionNoHuman-readable note (e.g. 'OIDC client secret for Grafana')

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv0.11.0
    • addedInput schema / properties / domain
      Added value: +{
+  "description": "Name of the key domain to encrypt to / decrypt with. Optional. Defaults to the domain recorded in the file's _meta_unencrypted block, and failing that to 'default'. Call sops_list_domains to see what this server has configured.",
+  "type": "string"
+}
  2. First observedv0.10.0

TDQS

A4.3/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does well: it discloses the secret's format (64-char alphanumeric), the hash algorithm (PBKDF2-SHA512), that both are stored together in a new encrypted file, and that the hash is returned in the response for pasting into Authelia config. It omits auth/permission requirements and whether an existing file/key is overwritten.

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

Conciseness4/5

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

The first sentence front-loads the purpose, and subsequent sentences add concrete, non-redundant detail. It is somewhat dense but every sentence earns its place; no filler.

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?

For a tool with no output schema and no annotations, the description adequately covers what is created, how it is stored, and what is returned (the hash). Minor gaps remain around overwrite behavior and required permissions, but the call can be made correctly from what is provided.

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 the baseline is 3, but the description adds meaning beyond the schema by spelling out the KEY_NAME/KEY_NAME_HASH naming relationship and the returned hash. It does not add syntax detail for domain or description, but those are already documented in the schema.

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?

States a specific verb and resource ('create an Authelia-compatible OIDC client secret') and enumerates exactly what gets produced (KEY_NAME generated secret plus KEY_NAME_HASH derived hash). It also distinguishes itself from sibling sops_create_secrets by framing itself as a convenience wrapper.

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?

Explicitly routes the agent by stating it is 'Equivalent to calling sops_create_secrets with one generated and one derived (pbkdf2_sha512_authelia) entry', which tells the agent when to prefer this shortcut versus the general tool. It does not state when NOT to use it, but the convenience framing makes the boundary clear.

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

Deploy Server

Other Tools