Skip to main content
Glama

Coding Agent Changelog Check

Recent changes of a coding-agent CLI

recent_changes
Read-onlyIdempotent

Latest versions of a coding-agent CLI with their changelog items. Set breaking_only to see only removals, renames and default changes.

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

Input Schema

NameRequiredDescriptionDefault
toolYesclaude-code, codex, or gemini-cli
versionsNo
breaking_onlyNo

Output Schema

NameRequiredDescriptionDefault
entriesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the agent knows this is a safe repeatable local read. The description adds that results carry changelog items and what the breaking_only filter actually includes, but says nothing about result volume, ordering, or how many versions come back by default.

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 with no filler, and the primary purpose is front-loaded ahead of the filter hint. Every clause earns its place.

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-value explanation is not required. However, with two of three parameters undocumented in the schema and one of those unexplained in the description, the definition is not quite complete for a tool with a bounded 'versions' argument.

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 33% — only 'tool' is documented in the schema. The description meaningfully defines 'breaking_only' (removals, renames, default changes), which is a real addition beyond the schema, but it leaves 'versions' entirely unexplained (presumably a count, bounded 1-30) in both schema and description.

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 resource and payload: 'Latest versions of a coding-agent CLI with their changelog items,' which tells an agent exactly what it retrieves. It does not differentiate from the only sibling (check_usage), but that sibling is far enough in domain that confusion is unlikely.

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?

Offers one concrete conditional: 'Set breaking_only to see only removals, renames and default changes,' which is useful invocation guidance. It gives no broader when-to-use/when-not context and no mention of alternatives or of when the un-filtered call is preferable.

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