Skip to main content
Glama
Sign In

Frostbyte

by dev.getfrostbyte
OverviewDiscussionsAdmin

create_release

Create a new release or milestone in a project. Omit name to apply the project's release-naming pattern (e.g. previous v1.2.0 → v1.2.1, Sprint 47 → Sprint 48).

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": {
      "projectId": "<projectId>",
      "context": "<context>"
    },
    "name": "create_release"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoShort release name (e.g. 'v1.2', 'May sprint'), max 40 characters. If omitted, the server suggests the next name from the project's last release.
colorNoOmit to get the palette colour other releases use least. Set only when the user asks for a colour: pick the closest of #6366f1, #f97316, #22c55e, #ec4899, #06b6d4, #f59e0b, #8b5cf6, #14b8a6, #f43f5e, #3b82f6, avoiding one another release already uses (list_releases shows them), unless they give an exact 6-digit hex.
statusNoRelease status (default: upcoming). Setting active moves the current active release to upcoming.
contextYesExplain why you are calling this tool and how it fits into the user's overall goal. This parameter is used for analytics and user intent tracking. YOU MUST provide 15-25 words (count carefully). NEVER use first person ('I', 'we', 'you') - maintain third-person perspective. NEVER include sensitive information such as credentials, passwords, or personal data. Example (20 words): "Searching across the organization's repositories to find all open issues related to performance complaints and latency issues for team prioritization."
projectIdYesThe project ID
launchDateNoLaunch date (ISO 8601) for a release created as completed, to backdate when it really shipped. Defaults to now when completed. Setting it sends no emails and publishes nothing.
targetDateNoTarget date (ISO 8601, e.g. 2025-12-31)
descriptionNo1–2 short factual sentences on what this release covers and why. Always write one; release notes drafts build on it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare this a non-destructive, non-idempotent, open-world write, and the schema documents the side effects (status change demoting the active release, launchDate sending no emails). The description adds the naming-pattern behavior, but that repeats what the `name` property already says, so net value beyond structured fields is modest without being wrong.

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?

Two short sentences, front-loaded with the action and followed by the single most useful calling nuance. The second sentence slightly duplicates schema text, but it is compact and earns most of its space as a quick reference.

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?

For an eight-parameter creation tool with no output schema, the description covers only the naming behavior and leaves color, status transition, and date semantics entirely to the schema. That is acceptable given 100% schema coverage and safety-bearing annotations, but the description itself does not fully prepare an agent for the tool's side effects.

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 description coverage is 100%, so the parameters are already richly documented in the schema. The description's naming-pattern example (v1.2.0 → v1.2.1, Sprint 47 → Sprint 48) illustrates default-name behavior but is redundant with the `name` field's own description, so baseline 3 applies.

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 names a specific verb and resource ('Create a new release or milestone in a project'), which is enough to distinguish it from update_release, get_release, and list_releases by implication. It stops short of naming those siblings explicitly, so there is room to be sharper about what this tool is not.

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?

It gives one concrete usage rule ('Omit `name` to apply the project's release-naming pattern'), which tells the agent how to call it, but offers no when-not conditions and no routing to alternatives such as update_release when the release already exists. Usage is implied rather than stated.

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

All Frostbyte toolsInspect
Try in Browser
Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources