Havoptic AI Release Intelligence

Search changes

search_changes

Read-onlyIdempotent

Search typed change items (title + evidence) and, unless kinds is set, legacy release notes — flags, error strings, feature names, config keys. Successor to search_release_notes. Brief mode returns snippets only.

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": {
      "query": "<query>"
    },
    "name": "search_changes"
  }
}

Input Schema

Name	Required	Description
`kinds`	No	Change kinds to include, e.g. ['breaking','security'].
`limit`	No	Max results per section (default 10)
`query`	Yes	Search terms, e.g. 'MCP OAuth' or '--dangerously-skip-permissions'
`since`	No
`tools`	No	Tool ids (fuzzy: 'claude', 'codex', 'copilot' resolve). Omit for all tools; see list_tools.
`until`	No

Output Schema

Name	Required	Description	Default
`items`	Yes
`query`	Yes
`object`	Yes
`omitted`	No
`releases`	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

A4/5.0

Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive and closed-world, so the safety profile is covered; the description adds genuinely new behavior — that legacy release notes are included by default unless kinds is supplied, and that a brief mode returns snippets only. The brief-mode mention is, however, untethered: no 'brief' parameter exists in the schema, leaving the agent unsure how to trigger it.

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 tight, front-loaded sentences cover identity, scope, and the key default behavior with no filler. The trailing 'Brief mode returns snippets only' is dangling since it references a capability the schema does not expose, but the overall density is good.

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?

A read-only search with an output schema needs little return-value explanation, and the description's scope notes cover the important default behavior. However, with 6 parameters and since/until undocumented anywhere plus an unaddressable 'brief mode', an agent cannot fully determine supported filtering from this definition alone.

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 coverage is 67%, and the description adds meaning only for kinds (its effect on legacy note inclusion). The two undocumented parameters, since and until, are never mentioned in the description either, so date-scoping semantics remain entirely undisclosed. Baseline 3 is appropriate for a mid-coverage schema where the description does not compensate for the gap.

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 and resource ('search typed change items') and enumerates what is actually matched (flags, error strings, feature names, config keys), which is far more concrete than the title. It also explicitly names its predecessor search_release_notes, letting an agent place it against a sibling without opening either schema.

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?

'Successor to search_release_notes' gives a clear routing signal, and 'unless kinds is set, legacy release notes' is searched describes a real behavioral condition for choosing whether to pass kinds. There is no explicit when-not guidance (e.g. when to use get_breaking_changes or whats_changed_since instead), so it stops short of full alternative coverage.

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?