compare_distro_releasesCompare package additions, removals and version changes between two releases.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | ||
| from | Yes | ||
| limit | No | ||
| query | No | ||
| change | No | ||
| distro | Yes |
Changes observed during successful MCP inspections. Dates show when Glama detected each change.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already disclose readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the specific comparison dimensions but does not disclose behavior like default limits, filtering semantics, or output format. No contradiction with annotations.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, front-loaded sentence with no wasted words. It efficiently communicates the core purpose and scope.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With six parameters and no output schema, the description is too sparse for an agent to correctly invoke the tool. It omits parameter semantics, filtering options, and any contextual details about what the output contains, leaving critical gaps.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 0%, and the description does not explain the parameters from, to, distro, limit, query, or change. The phrase 'package additions, removals and version changes' loosely maps to some change enum values but does not clarify required arguments or filter behavior.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states 'Compare package additions, removals and version changes between two releases,' specifying a concrete action and scope. It distinguishes itself from siblings like compare_distros and compare_package_versions by focusing on release-to-release package changes.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
No guidance is provided on when to use this tool versus alternatives such as compare_distros or compare_package_versions. The description only states what it does without exclusions, prerequisites, or selection criteria.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
The tool set covers many closely related operations: three 'compare_*' tools, four command-diagnostic tools, and several lookup tools that can overlap. Descriptions help but boundaries are not always obvious (e.g., identify_binary vs query_file_provides, lint_command vs suggest_fix), so an agent may select the wrong tool for a task.
All tool names follow a consistent verb_noun (or verb_noun_noun) pattern with snake_case. Verbs such as get, search, compare, and diagnose are used predictably, making the set's structure easy to learn.
22 tools is more than the typical well-scoped set (3-15), and the server covers a broad but unified domain. While each tool serves a distinct purpose, the granularity is slightly heavy—some comparison and diagnostic tools could potentially be merged.
The tool surface covers core intelligence workflows: searching, fetching details, comparing, resolving installs, migration planning, lifecycle checks, and vulnerability lookup. Minor gaps exist such as a direct 'list_distributions' tool, but agents can work around these using existing tools.