Havoptic AI Release Intelligence

Get one release

get_release

Read-onlyIdempotent

One release by id (e.g. 'claude-code-2.1.183', canonical 'claude-code@2.1.183') or by tool + version ('latest' allowed). detail=full (the default for a bare id lookup, as before) includes complete release notes; brief/standard omit them unless include_raw_notes is true.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "get_release"
  }
}

Input Schema

Name	Required	Description
`id`	No	Canonical (tool@version) or legacy (tool-version) release id
`tool`	No	Tool id (fuzzy), used with version
`detail`	No	brief (default) omits infographics and raw notes; standard adds evidence and links; full adds complete release notes.
`version`	No	Semver or 'latest'
`include_raw_notes`	No	Include the full upstream notes in any detail mode

Output Schema

Name	Required	Description	Default
`object`	Yes
`omitted`	No
`release`	Yes
`truncated`	Yes
`next_cursor`	Yes
`freshness_note`	No
`estimated_tokens`	No
`dataset_updated_at`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 2, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive), so the description earns credit for adding genuine behavioral context: detail=full is the default for a bare id lookup, and brief/standard suppress notes unless include_raw_notes is true. Worth noting the description's 'full is the default for a bare id lookup' sits in tension with the schema's 'brief (default)', which an agent must reconcile.

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?

Two sentences, front-loaded with the lookup contract before the detail-mode nuance. Parentheticals carry real information (examples, alternative id form, the 'as before' compatibility note) rather than filler.

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?

An output schema exists so return values need no explanation, and the detail semantics are covered. However, all five parameters are optional, and the description never says which combination is required or what happens if id and tool/version are both supplied or both omitted — a real ambiguity for a zero-required-param tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so baseline is 3, but the description adds meaning beyond it: it supplies concrete id formats (canonical 'claude-code@2.1.183' vs legacy 'claude-code-2.1.183'), clarifies 'latest' is legal for version, and explains the detail x include_raw_notes interaction rather than just listing enum values.

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?

States a specific verb+resource (fetch one release) and enumerates the two lookup keys: release id (with concrete example, canonical and legacy forms) or tool + version. That distinguishes it from list-shaped siblings like release_history, get_latest_releases, and latest_releases, though none are named explicitly.

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?

Usage is implied by the lookup modes and the 'latest' allowance, and the detail-mode sentence hints at when brevity matters. But it never states when to prefer this over get_latest_releases, release_history, or get_upgrade_notes, nor what to do when the release is not found.

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

All Havoptic AI Release Intelligence tools Inspect

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

Need Help?