Skip to main content
Glama
Sign In

Havoptic AI Release Intelligence

by com.havoptic
OverviewDiscussionsAdmin

Release history

release_history
Read-onlyIdempotent

Deprecated: use get_latest_releases with since. Release history for one tool within an optional date window (newest first). Summaries only; use get_release for full notes. Default detail=brief omits infographic URLs.

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": {
      "tool": "<tool>"
    },
    "name": "release_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolYesTool id, e.g. 'claude-code', 'openai-codex', 'cursor', 'gemini-cli', 'kiro', 'github-copilot', 'windsurf', 'antigravity-cli', 'grok-build', 'cline', 'opencode', 'zed', 'factory-droid', 'devin', 'lovable', 'amp', 'copilot-vscode', 'replit-agent', 'bolt', 'v0', 'openai-platform', 'anthropic-api', 'gemini-api', 'xai-api', 'mistral-api', 'deepseek-api', 'amazon-bedrock', 'gemini-agent-platform', 'mcp-spec', 'openai-agents-python', 'openai-agents-js', 'claude-agent-sdk-python', 'claude-agent-sdk-typescript', 'vercel-ai-sdk', 'langgraph-python', 'langgraph-js', 'llamaindex', 'crewai', 'mastra', 'cloudflare-agents-sdk', 'ollama', 'vllm', 'lm-studio', 'huggingface-transformers'. Use list_tools for the live list.
limitNoMax releases to return (default 50)
sinceNoOnly releases on/after this ISO date (e.g. '2026-01-01')
untilNoOnly releases on/before this ISO date
detailNobrief omits infographics and fullNotes; full includes complete notes on single-release reads.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower; the description still adds ordering ('newest first'), output granularity ('summaries only'), and the brief-mode omission of infographic URLs. It doesn't say whether the deprecated tool still returns data or will be removed, which is the one behavioral fact an agent would still want.

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?

Four short clauses, zero filler, with the deprecation warning and the replacement tool front-loaded before any behavioral detail. Every sentence carries distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 5-parameter read tool with no output schema, the definition covers scope, ordering, output granularity, defaults, and a migration path. The only gap is the lifecycle status of the deprecated endpoint, but the redirect is sufficient for correct tool selection.

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; the description earns extra by documenting the default value of detail ('default detail=brief'), which the schema's detail property does not state, and by clarifying the summaries-only output in relation to that parameter. Date-window semantics for since/until are already fully covered by the schema.

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?

Names a specific verb+resource and scope: 'Release history for one tool within an optional date window (newest first).' It explicitly separates itself from two siblings — get_release for full notes and get_latest_releases as the replacement — so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

Explicit routing: 'Deprecated: use get_latest_releases with since' tells the agent when NOT to use this tool, and 'use get_release for full notes' names the alternative for the deep-dive case. Both conditions are stated rather than inferred.

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 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