Skip to main content
Glama
nickbaumann98

Release Notes MCP Server

configure_template

Set up a custom template for generating release notes, allowing you to define the structure and format for your project's changelog.

Instructions

Configure a custom template for release notes

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYes
templateYes

Implementation Reference

  • Handler logic for the 'configure_template' tool: parses input arguments, stores the custom template in a global 'templates' object, and returns a JSON success message.
    case 'configure_template': {
      const args = ConfigureTemplateSchema.parse(request.params.arguments);
      templates[args.name] = args.template;
    
      return {
        content: [
          {
            type: 'text',
            text: JSON.stringify({ message: `Template '${args.name}' configured successfully` }),
          },
        ],
      };
    }
  • Zod schema defining the input for 'configure_template': requires 'name' (string) and 'template' (string).
    export const ConfigureTemplateSchema = z.object({
      name: z.string(),
      template: z.string()
    });
  • Tool registration in the ListTools handler: specifies name, description, and converts schema to JSON schema.
    {
      name: 'configure_template',
      description: 'Configure a custom template for release notes',
      inputSchema: zodToJsonSchema(ConfigureTemplateSchema),
    },
  • Global object storing configured templates, used by both 'configure_template' and 'generate_release_notes' tools.
    const templates: Record<string, string> = {};
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 'configure' but doesn't clarify if this creates a new template, updates an existing one, or performs another action. There's no information on permissions, side effects, or response format, leaving significant gaps in understanding the tool's behavior beyond its basic purpose.

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, efficient sentence that directly states the tool's purpose without unnecessary words. It is appropriately sized and front-loaded, making it easy to parse quickly. Every word earns its place, contributing to clarity without redundancy.

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?

Given the complexity of a configuration tool with no annotations, 0% schema description coverage, and no output schema, the description is incomplete. It lacks details on behavioral traits, parameter meanings, and expected outcomes, making it insufficient for an AI agent to fully understand how to invoke the tool correctly in context.

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?

The input schema has 0% description coverage, so the description must compensate. It mentions 'configure a custom template' but doesn't explain the parameters 'name' and 'template', such as what they represent (e.g., template identifier vs. content) or any constraints. This adds minimal value beyond the schema, failing to adequately address the coverage gap.

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 ('configure') and the resource ('a custom template for release notes'), making the tool's purpose understandable. It distinguishes from sibling tools like 'analyze_commits' and 'generate_release_notes' by focusing on template configuration rather than analysis or generation. However, it doesn't specify what 'configure' entails (e.g., create, update, or set), keeping it from a perfect score.

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 prerequisites, such as needing existing templates or specific contexts, nor does it differentiate usage from sibling tools like 'generate_release_notes', which might involve templates. This lack of explicit when-to-use or when-not-to-use information limits its utility for an AI agent.

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/nickbaumann98/release-notes-server'

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