Skip to main content
Glama
Sign In

Havoptic AI Release Intelligence

by com.havoptic
OverviewDiscussionsAdmin

Latest releases

latest_releases
Read-onlyIdempotent

Deprecated: use get_latest_releases. Most recent AI coding tool releases (newest first), optionally filtered to one tool. Returns summaries; use get_release for full notes. Default detail=brief omits infographic URLs.

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": "latest_releases"
  }
}

Input Schema

NameRequiredDescriptionDefault
toolNoTool 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 10)
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.4/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, but the description still adds useful behavior: results are newest-first, they are summaries rather than full notes, and the default detail=brief omits infographic URLs. It stops short of stating the response shape or any pagination semantics, which is the only remaining gap.

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 dense clauses, each earning its place: deprecation routing first, then what is returned, then the default detail behavior. Zero filler and the most action-deciding information is front-loaded.

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?

With no output schema, the description correctly tells the agent that only summaries come back and points to get_release for full notes, plus it explains the detail default. It never clarifies how 'tool' interacts with 'limit' or what a summary entry contains, but for a deprecated 3-param read tool this is close to sufficient.

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 tool list, the limit default of 10, and the brief/standard/full enum are already fully documented in structured fields. The description adds only the 'brief omits infographic URLs' nuance, which largely restates the schema's note that brief omits infographics and fullNotes.

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?

States a specific verb+resource ('Most recent AI coding tool releases'), the ordering (newest first), and the optional scope filter (one tool). It also immediately flags itself as deprecated and names the replacement, so an agent can tell it apart from get_latest_releases and get_release without opening a 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?

Explicitly says not to use this ('Deprecated: use get_latest_releases') and routes to a second sibling for a different need ('use get_release for full notes'). That is both a when-not and two named alternatives, leaving nothing to inference.

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