Skip to main content
Glama
Sign In
MCP Prompt Manager

MCP Prompt Manager

by Tae4an
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

get-template-details

Retrieve detailed information about a specific prompt template by providing its template ID (e.g., 'category.template').

Instructions

Get detailed information about a specific template

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": {
      "templateId": "<templateId>"
    },
    "name": "get-template-details"
  }
}

Input Schema

NameRequiredDescriptionDefault
templateIdYesTemplate ID (format: category.template)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

C2.9/5.0
Behavior2/5

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

The description implies a read-only operation ('Get detailed information'), but there are no annotations to confirm safety. No details are given about side effects, authentication requirements, rate limits, or response format. The tool is likely non-destructive, but this is not explicit.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single concise sentence that is front-loaded with the purpose. It contains no unnecessary words. However, it could include a bit more detail without becoming verbose.

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 single parameter and no output schema or annotations, the description is adequate but incomplete. It does not specify what 'detailed information' includes, which may force the agent to infer or guess. The tool is simple, but more context would improve usability.

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 input schema has 100% description coverage, so the baseline is 3. The tool description adds no extra meaning beyond the schema. It does not provide usage examples or additional context for the 'templateId' parameter.

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 it retrieves detailed information about a specific template. The verb 'Get' matches the tool name, and the resource is specified as 'a specific template', distinguishing it from list/search tools. However, it does not explicitly differentiate from similar 'get' tools like 'get-prompt'.

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?

No guidance is provided on when to use this tool vs alternatives. There is no mention of prerequisites, context, or situations where this tool should be preferred over siblings like 'search-templates' or 'list-templates'.

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