Skip to main content
Glama
MCP Prompts Server

MCP Prompts Server

by sparesparrow

Get a prompt

get_prompt
Read-onlyIdempotent

Retrieve one prompt by ID as JSON, including content, description, tags, and template variables; return an error naming the ID if no matching prompt is served.

Instructions

Get one prompt by id, as JSON: its content, description, tags, and for a template the variables it needs. Fails with an error naming the id when no such prompt is served.

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": {
      "id": "<id>"
    },
    "name": "get_prompt"
  }
}

Input Schema

NameRequiredDescriptionDefault
idYesPrompt ID, as returned by list_prompts

Output Schema

NameRequiredDescriptionDefault
idYes
nameYes
tagsYes
contentYes
versionYes
categoryNo
metadataNo
createdAtYes
updatedAtYes
variablesNo
isTemplateYes
descriptionNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv4.1.0
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / id / minLength
      Added value: +1
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "$schema": "http://json-schema.org/draft-07/schema#",
      +  "additionalProperties": {},
      +  "properties": {
      +    "category": {
      +      "type": "string"
      +    },
      +    "content": {
      +      "type": "string"
      +    },
      +    "createdAt": {
      +      "type": "string"
      +    },
      +    "description": {
      +      "type": "string"
      +    },
      +    "id": {
      +      "type": "string"
      +    },
      +    "isTemplate": {
      +      "type": "boolean"
      +    },
      +    "metadata": {
      +      "additionalProperties": {},
      +      "propertyNames": {
      +        "type": "string"
      +      },
      +      "type": "object"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "tags": {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    "updatedAt": {
      +      "type": "string"
      +    },
      +    "variables": {
      +      "items": {
      +        "anyOf": [
      +          {
      +            "type": "string"
      +          },
      +          {
      +            "additionalProperties": {},
      +            "properties": {
      +              "name": {
      +                "type": "string"
      +              }
      +            },
      +            "required": [
      +              "name"
      +            ],
      +            "type": "object"
      +          }
      +        ]
      +      },
      +      "type": "array"
      +    },
      +    "version": {
      +      "type": [
      +        "number",
      +        "string"
      +      ]
      +    }
      +  },
      +  "required": [
      +    "id",
      +    "name",
      +    "content",
      +    "isTemplate",
      +    "tags",
      +    "version",
      +    "createdAt",
      +    "updatedAt"
      +  ],
      +  "type": "object"
      +}
  2. Changed1 schema field changedv4.0.2
    • removedInput schema / additionalProperties
      Removed value: -false
  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?

Annotations already establish readOnly, idempotent, and non-destructive, so the bar is lower. The description still adds real value by disclosing the failure mode (an error that names the id) and by noting that `variables` only appear for templates, which the annotations cannot convey.

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, front-loaded with the core action and result shape, then the error condition. 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?

With an output schema and full annotation coverage, the description only needs to cover selection and failure behavior, which it does. It could add a hint about what the JSON envelope looks like on error (code vs message), but otherwise nothing essential is missing for a single-parameter read.

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 coverage is 100% and the single `id` parameter is documented as coming from list_prompts, so the schema carries the semantics. The description adds only the implicit notion of a served prompt id, which is marginal beyond the schema.

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 ("Get one prompt by id") and scopes it to a single record, which naturally separates it from list_prompts. It does not name a sibling explicitly, so it stops just short of a 5.

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?

Usage is implied by "by id" and the reference to list_prompts in the schema, so an agent can infer this is the follow-up call once it has an id. There is no explicit when-to-use or when-not guidance, and no named alternative such as get_stats or apply_template.

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