Skip to main content
Glama
Sign In
release-mcp

release-mcp

by stevedevex
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

validate_manifest

Check a release manifest YAML for validation errors without applying changes. Returns validity status with topology summary or exact error details.

Instructions

Validate a release manifest YAML without touching anything.

Returns 'valid' with a topology summary, or the exact validation error. Use before committing manifest changes to the state repo.

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": {
      "manifest_yaml": "<manifest_yaml>"
    },
    "name": "validate_manifest"
  }
}

Input Schema

NameRequiredDescriptionDefault
manifest_yamlYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4/5.0
Behavior4/5

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

Discloses that the tool is read-only ('without touching anything') and describes the return values ('valid' with summary or error). No annotation provided, so description carries burden and does so adequately.

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?

Three concise sentences with no extraneous information; key information is front-loaded.

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?

Low complexity and presence of output schema reduce need for return details, but parameter information is incomplete. Overall adequate but not exhaustive.

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?

With 0% schema description coverage, the description should detail the single parameter. It merely names it ('manifest YAML') without format, examples, or constraints.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it validates a release manifest YAML with no side effects, distinguishing it from sibling tools that perform other release operations.

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

Usage Guidelines4/5

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

Explicitly advises to use before committing manifest changes, providing clear context. However, no exclusions or alternatives are mentioned.

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