Skip to main content
Glama
lumile

Promptopia MCP

by lumile

get_prompt

Retrieve a specific prompt from Promptopia MCP using its unique ID to access stored prompt content for reuse.

Instructions

Gets a prompt by its ID

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
idYesID of the prompt to retrieve

Implementation Reference

  • MCP tool handler execution for 'get_prompt': extracts 'id' from input arguments, calls PromptsService.getPrompt(id), and returns the result serialized as JSON text content in MCP format.
    case 'get_prompt': {
      const { id } = args
      const result = await this.promptsService.getPrompt(id)
      return {
        content: [{
          type: 'text',
          text: JSON.stringify(result, null, 2)
        }]
      }
    }
  • Registration of the 'get_prompt' tool in listTools(), including name, description, and input JSON schema requiring 'id' parameter.
    {
      name: 'get_prompt',
      description: 'Gets a prompt by its ID',
      inputSchema: {
        type: 'object',
        properties: {
          id: {
            type: 'string',
            description: 'ID of the prompt to retrieve'
          }
        },
        required: ['id']
      }
    },
  • JSON schema definition for 'get_prompt' tool input, specifying object with required 'id' string property.
    inputSchema: {
      type: 'object',
      properties: {
        id: {
          type: 'string',
          description: 'ID of the prompt to retrieve'
        }
      },
      required: ['id']
    }
  • Supporting method in PromptsService that implements the core retrieval logic: validates ID, reads prompt JSON from filesystem, and throws appropriate errors if not found.
    async getPrompt(id: string): Promise<Prompt> {
      if (!id || !id.trim()) {
        throw new ValidationError('Prompt ID is required')
      }
    
      try {
        const filePath = path.join(this.promptsDir, `${id}.json`)
        return await this.fileSystemService.readJSONFile<Prompt>(filePath)
      } catch (error) {
        if (error instanceof Error && error.message.includes('not found')) {
          throw new NotFoundError(`Prompt not found: ${id}`)
        }
        throw error
      }
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool 'Gets a prompt,' implying a read-only operation, but doesn't specify whether it requires authentication, what happens if the ID is invalid (e.g., returns an error or null), or any rate limits. This leaves significant gaps in understanding the tool's behavior.

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 a single, clear sentence with zero waste: 'Gets a prompt by its ID.' It is appropriately sized and front-loaded, efficiently conveying the core purpose without unnecessary details.

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

Completeness3/5

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

Given the tool's low complexity (one parameter, no output schema, no annotations), the description is minimally adequate. It states what the tool does but lacks context on usage, behavioral traits, or output, making it incomplete for effective agent use without additional inference or trial.

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?

The schema description coverage is 100%, with the single parameter 'id' fully documented in the schema as 'ID of the prompt to retrieve.' The description adds no additional meaning beyond this, such as format examples (e.g., UUID) or constraints, so it meets the baseline of 3 where the schema does the heavy lifting.

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?

The description clearly states the action ('Gets') and resource ('a prompt') with a specific identifier ('by its ID'), making the purpose immediately understandable. However, it doesn't differentiate this tool from its siblings like 'list_prompts' or 'apply_prompt', which would require mentioning this is for retrieving a single prompt by ID rather than listing multiple or applying one.

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

Usage Guidelines2/5

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

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention that this is for retrieving a single prompt by ID, as opposed to 'list_prompts' for multiple prompts or 'apply_prompt' for using a prompt, nor does it specify prerequisites like needing a valid prompt ID.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/lumile/promptopia-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server