Skip to main content
Glama

Create secret

create_secret
Destructive

Create an organisation secret whose value Ankra generates - a random value nobody sees, you included - for a credential that only has to match between the parts that use it (a database password, a signing key, a shared token). Answers with the secret's ${SECRET_SLOT:} sentinel; put the sentinel where the value belongs and Ankra resolves and seals it at deploy. The secret has no expiry: it stays until a person deletes it. It never takes a value: for a secret the person already has, use request_secret.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "create_secret"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameYesA name for the secret, unique in the organisation, e.g. 'langfuse-db-password' (at most 120 characters, one line).
lengthNoOptional length of the generated value, 16 to 96 characters. Defaults to the platform's minted length.
prefixNoOptional fixed text the generated value starts with, when the consumer expects one (e.g. 'sk-').
descriptionNoOptional note on what the secret is for (at most 240 characters).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  2. Added

TDQS

A4.5/5.0
Behavior5/5

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

Goes well past the annotations by disclosing that the value is generated and never visible, that the tool returns a ${SECRET_SLOT:<id>} sentinel which Ankra resolves and seals at deploy, and that the secret has no expiry and persists until a person deletes it. The last point is important given destructiveHint=true: the agent learns that creation has a lasting, human-cleaned-up effect.

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?

Front-loaded with the verb, resource and generated-value contract, and every sentence carries information about return value, lifecycle or alternatives. The aside "you included" is slight flavor but reinforces the never-visible property, so it is not dead weight.

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 four-parameter creation tool with no output schema, it supplies the key missing piece an agent would otherwise need: the return shape (a sentinel to place where the value belongs). Only minor gaps remain, such as what the response looks like if the name collides, which the schema's uniqueness note only partially covers.

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 already explains name, length, prefix and description fully. The prose adds no per-parameter detail beyond what the schema carries (it never mentions length bounds or prefix behavior), so this lands at the baseline rather than above it.

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 organisation secret") plus the defining trait that Ankra generates the value and the caller never supplies it. It also names the sibling it is not ("for a secret the person already has, use request_secret"), so an agent can separate it from request_secret without opening either schema.

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?

Gives an explicit when-to-use criterion (a credential that only has to match between the parts that use it, with concrete examples: database password, signing key, shared token) and an explicit when-not-to criterion with the alternative tool named. Both directions are covered, not just the happy path.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.