Skip to main content
Glama
Sign In
sparesparrow

MCP Prompts Server

by sparesparrow
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

add_prompt

Creates and stores a new prompt, optionally as a template with defined variables so apply_template can fill it at runtime.

Instructions

Add a new prompt. Set isTemplate and variables to make it a template that apply_template can fill.

Input Schema

NameRequiredDescriptionDefault
nameYes
tagsNo
contentYes
metadataNo
variablesNo
isTemplateNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. 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"
+  }
+]
  2. First observedv4.0.0

TDQS

B3/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full behavioral burden. For a creation/mutation tool it discloses nothing about uniqueness constraints on name, error behavior, or persistence side effects, only the template flag's effect.

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?

Two short sentences with zero filler, and the primary action is front-loaded ahead of the template hint.

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

Completeness2/5

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

A 6-parameter creation tool with a nested variables structure, no annotations, and no output schema needs far more disclosure about required inputs and mutation behavior than this two-sentence description provides.

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

Parameters2/5

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

Schema description coverage is 0% across 6 parameters, so the description must compensate. It only explains 2 of them (isTemplate, variables) and says nothing about name, content, tags, or the nested metadata object, leaving required fields and variable object shape undocumented.

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 the template-creation mode by naming the sibling consumer, apply_template. This distinguishes it from read/list siblings, though it does not explicitly contrast with update_prompt.

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?

Implies when to use the template path ("Set isTemplate and variables... that apply_template can fill"), but gives no explicit when-to-use vs update_prompt guidance, and no mention of duplicate-name behavior or prerequisites.

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