Skip to main content
Glama

Coding Agent Changelog Check

Check a flag or command against recent changes

check_usage
Read-onlyIdempotent

Search the official changelog of a coding-agent CLI for a flag, command or setting (e.g. '--full-auto', 'claude -p', 'permission mode'). Returns known (verified usage changes, incl. ones not in recent release notes) and hits (matching changelog entries, newest first; breaking=true marks removals, renames and default changes). Empty results mean no recorded change in the fetched history.

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

Input Schema

NameRequiredDescriptionDefault
toolYesclaude-code, codex, or gemini-cli
queryYes

Output Schema

NameRequiredDescriptionDefault
hitsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already establish that this is a read-only, idempotent, closed-world operation. The description adds useful behavior beyond that: it explains the `known` and `hits` return concepts, says hits are newest first, defines `breaking=true`, and explains what empty results mean.

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?

The description is three dense sentences, front-loading the purpose and then covering return semantics and empty results. It is efficient and largely free of filler, though the return-value detail could be tightened given the output schema.

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 two-parameter read-only search tool with annotations and an output schema, the description provides enough context to call it correctly and interpret empty results. The main remaining gap is that it does not route the agent between this tool and `recent_changes`.

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 only 50%, so the description must help clarify parameters. It gives useful query examples such as `--full-auto` and `claude -p`, which compensates somewhat for the undocumented `query` parameter, but it adds little about choosing among the `tool` enum values beyond implying a coding-agent CLI.

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 states a clear verb and resource: search the official changelog for a flag, command, or setting, with concrete examples. It is distinguishable in general terms, but it does not explicitly contrast itself with the sibling `recent_changes` tool.

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?

The wording implies this tool is for checking a specific flag, command, or setting, and gives examples of those inputs. However, it gives no explicit when-to-use guidance versus `recent_changes`, nor does it state when this tool should be avoided.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources