Skip to main content
Glama

save_prompt

Call this the moment the user says anything like 'save this prompt', 'save this as a prompt', 'use nokbase to save this', 'keep this prompt', or 'I want to save/store/reuse this' about a piece of text, even if they don't use the word 'prompt' explicitly. This is the ONLY tool that saves text so it can be run again word-for-word in another AI tool later. Only prompt is required. Do not pause to ask the user for a name, slug, or description first; all three are generated automatically if left out, so call this immediately rather than stopping to gather more fields. Store the text exactly as-is: do not clean it up, shorten it, paraphrase it, or improve it. Do not use remember_brand_fact for this: it compresses text into a summary and will not preserve it word-for-word.

Input Schema

NameRequiredDescriptionDefault
nameNoShort human-readable name, title case, max 40 characters. Omit it — it's derived automatically from the prompt. If given, whatever length works — it's trimmed automatically.
slugNoURL-safe identifier. Omit it — it's derived automatically and kept unique. If given, any text works — it's normalized automatically, so don't worry about exact formatting.
brandNoWhich of the user's brands this is for, by name. Leave it out to use this connection's default brand. Set it when the conversation is about a different brand of theirs. If you can't tell which brand is meant, ask the user first.
promptYesThe prompt text, verbatim, exactly as the user wrote or generated it. The only required field.
categoryNoCategory. One of: general, video, writing, code, design, research, marketing, other. Default: general. An unrecognized value falls back to general rather than failing.
descriptionNoOne sentence on what this prompt is for. Optional — fine to omit.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Beyond the annotations, the description explains important behavior: optional fields are auto-generated, the text must be stored verbatim without cleanup, and this tool is the exclusive verbatim save path. These details directly affect how the agent should invoke the tool and guard against incorrect use.

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 front-loaded with the primary trigger and purpose, followed by the exclusivity claim, required-field guidance, and the key verbatim/alternative-use caution. Each sentence contributes useful selection or invocation guidance without unnecessary digressions.

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?

The description thoroughly covers when to call the tool, required and optional fields, verbatim storage behavior, and a relevant alternative to avoid. The main gap is that there is no output schema and the description does not explain what the tool returns after saving, though that is a minor omission for a save action.

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 all six parameters are already well documented. The description reinforces that only prompt is required and that name, slug, and description can be omitted, but this largely repeats schema-level guidance rather than adding new parameter semantics.

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 that this tool saves prompt text for reuse and explicitly calls out that it is the only tool that preserves text word-for-word. It also distinguishes itself from remember_brand_fact, which compresses text, so an agent can confidently choose this tool over siblings.

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?

It gives concrete trigger phrases and conditions for calling the tool, including cases where the user does not say 'prompt' explicitly. It also names a specific alternative not to use and explains why, and tells the agent not to pause to gather optional fields.

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.

Resources