Skip to main content
Glama
MCP Prompts Server

MCP Prompts Server

by sparesparrow

Add a prompt

add_prompt

Save a new prompt with a name and content, optionally as a reusable template with variables, so it can be organized and filled at runtime.

Instructions

Add a new prompt. Set isTemplate and variables to make it a template that apply_template can fill. Give id to choose a stable id (it fails if the id is taken); otherwise a random one is assigned. The result says whether the prompt was saved to disk or is kept in memory only.

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>",
      "content": "<content>"
    },
    "name": "add_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idNoStable id for the new prompt. Left out, the server assigns a random one.
nameYes
tagsNo
contentYes
categoryNo
metadataNo
variablesNo
isTemplateNo
descriptionNo

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
versionYes
persistedYesTrue when the change was saved to the state directory, false when it is in memory only

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed9 schema fields changedv4.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / category
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / content / maxLength
      Added value: +1000000
    • addedInput schema / properties / content / minLength
      Added value: +1
    • addedInput schema / properties / description
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / id
      Added value: +{
      +  "description": "Stable id for the new prompt. Left out, the server assigns a random one.",
      +  "pattern": "^[A-Za-z0-9][A-Za-z0-9._-]{0,127}$",
      +  "type": "string"
      +}
    • addedInput schema / properties / name / minLength
      Added value: +1
    • changedInput schema / properties / variables / items / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "properties": {
      -      "description": {
      -        "type": "string"
      -      },
      -      "name": {
      -        "type": "string"
      -      },
      -      "required": {
      -        "default": true,
      -        "type": "boolean"
      -      },
      -      "type": {
      -        "default": "string",
      -        "enum": [
      -          "string",
      -          "number",
      -          "boolean"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "name"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "minLength": 1,
      +    "type": "string"
      +  },
      +  {
      +    "properties": {
      +      "description": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "minLength": 1,
      +        "type": "string"
      +      },
      +      "required": {
      +        "default": true,
      +        "type": "boolean"
      +      },
      +      "type": {
      +        "default": "string",
      +        "enum": [
      +          "string",
      +          "number",
      +          "boolean"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  }
      +]
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": false,
      +  "properties": {
      +    "id": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "persisted": {
      +      "description": "True when the change was saved to the state directory, false when it is in memory only",
      +      "type": "boolean"
      +    },
      +    "version": {
      +      "type": [
      +        "number",
      +        "string"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "name",
      +    "version",
      +    "persisted"
      +  ],
      +  "type": "object"
      +}
  2. Changed3 schema fields changedv4.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / metadata / propertyNames
      Added value: +{
      +  "type": "string"
      +}
    • changedInput schema / properties / variables / items / anyOf
      Previous value: -[
      -  {
      -    "type": "string"
      -  },
      -  {
      -    "additionalProperties": false,
      -    "properties": {
      -      "description": {
      -        "type": "string"
      -      },
      -      "name": {
      -        "type": "string"
      -      },
      -      "required": {
      -        "default": true,
      -        "type": "boolean"
      -      },
      -      "type": {
      -        "default": "string",
      -        "enum": [
      -          "string",
      -          "number",
      -          "boolean"
      -        ],
      -        "type": "string"
      -      }
      -    },
      -    "required": [
      -      "name"
      -    ],
      -    "type": "object"
      -  }
      -]New value: +[
      +  {
      +    "type": "string"
      +  },
      +  {
      +    "properties": {
      +      "description": {
      +        "type": "string"
      +      },
      +      "name": {
      +        "type": "string"
      +      },
      +      "required": {
      +        "default": true,
      +        "type": "boolean"
      +      },
      +      "type": {
      +        "default": "string",
      +        "enum": [
      +          "string",
      +          "number",
      +          "boolean"
      +        ],
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "name"
      +    ],
      +    "type": "object"
      +  }
      +]
  3. First observedv4.0.0

TDQS

A3.8/5.0
Behavior4/5

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

Beyond the non-read-only, non-idempotent annotations, it discloses two meaningful traits: an explicit id causes failure if taken, and the result reports whether the prompt was persisted to disk or held in memory only. Non-idempotency is thereby explained (random id per call) rather than merely declared. It does not mention permissions or size limits such as the 1MB content cap.

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?

Three short sentences, front-loaded with the core action, then the template/id behavior, then the return semantics. Every clause carries information not present elsewhere and nothing is redundant.

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?

An output schema exists so return values need no explanation, yet the description usefully flags the disk-vs-memory outcome. For a 9-parameter creation tool the main shortfall is field-level coverage of the remaining parameters, but the creation-specific behaviors an agent needs to call it correctly are present.

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 only 11% across 9 parameters, so the description must compensate, and it partly does by covering id, isTemplate, and variables. It adds nothing about name, content, tags, category, metadata, or the nested variable object shape (name/type/required/description), leaving the most structurally complex parameter under-explained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource ("Add a new prompt") and clarifies it creates a new prompt record rather than editing one. It also names a sibling, apply_template, in a way that clarifies the template relationship, though it never contrasts itself with update_prompt, the closest alternative.

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

Usage Guidelines3/5

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

Conditional guidance is implied rather than stated: it explains that setting isTemplate and variables makes the prompt fillable by apply_template, and that supplying id gives a stable id. There is no explicit "use this instead of update_prompt when..." instruction, so the caller must infer that this tool creates and update_prompt modifies.

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