Surface release notes likely to contain security or CVE fixes. Celestia-specific. Heuristic: matches release bodies containing security / CVE / vulnerability / patch keywords.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max rows (default 10). |
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?
Since no annotations are provided, the description carries the burden of behavioral disclosure. It does reveal the heuristic keyword-matching mechanism and the probabilistic 'likely' nature, which is useful. Yet it omits return format, ordering, and false-positive caveats, leaving some behavioral ambiguity.
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 two sentences with no filler: the first states the purpose, the second explains the heuristic. Information is front-loaded and every sentence earns its place.
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?
For a simple read-only tool with one optional parameter and no output schema, the description covers the core purpose and behavior adequately. Missing items like explicit return details and sibling differentiation are minor given how simple the tool is.
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?
The input schema covers the single `limit` parameter 100% with a clear description and default. The tool description adds no parameter-specific meaning, so the baseline score of 3 applies.
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 states a specific verb ('Surface') and a clearly scoped resource ('release notes likely to contain security or CVE fixes'). It also names the Celestia-specific heuristic, distinguishing it from general release-note tools like search_release_notes.
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?
The context is clear: use this when you need release notes that likely contain security/CVE fixes, and it explicitly scopes to Celestia. However, it does not name alternatives or provide explicit when-not-to-use guidance, so it stops short of full routing.
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.
Most tools target clearly distinct content types and actions, and descriptions carefully carve out boundaries (e.g. get_network_state vs get_network_stats, get_discussion vs get_github_discussion). However, the overlapping get_/find_/search_ families plus the very similar network_state/network_stats names leave some edge cases where an agent could select the wrong tool.
The dominant convention is verb_noun (find_*, get_*, list_*, search_*), and get/list/find roughly map to id-based retrieval, browsing, and discovery. Deviations like learning_path, ecosystem_dependency_graph, and semantic_search break the pattern, and the get_ vs find_ vs search_ boundaries are not perfectly predictable.
43 tools is on the high side for a single MCP server; even though the Celestia knowledge domain is broad, the surface is heavy and will increase selection cost. Most tools are individually useful, but the set would benefit from consolidation, e.g. merging release tools or search variants.
The server covers an unusually broad range of content types—CIPs, docs, forum, GitHub issues/discussions, releases, videos, whitepapers, ecosystem, and network state—with list/get/search access for most. Minor gaps remain, such as no dedicated blog retrieval and get_issue_status only returning status rather than full issue body, but core knowledge workflows have no dead ends.