get_freshness_summaryReturn a freshness-at-a-glance summary of the published catalogue: fresh, aging, stale, and reference counts plus the latest health check time.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds useful behavioral context by specifying the output categories and the health check timestamp, giving the agent a clearer expectation of what the tool reports.
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 filler. It immediately states the action and result, then lists the specific components of the summary. Every word 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 no-parameter, read-only summary tool, the description is complete. It states the scope ('published catalogue'), the output categories, and the health check time. The output schema exists to provide further return structure, so nothing essential is missing.
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 tool takes zero parameters, and the schema confirms this with 100% coverage of an empty properties set. There are no parameter semantics to clarify, so the baseline of 4 is appropriate; the description has no parameter burden to carry.
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 uses a specific verb ('Return') with a specific resource ('freshness-at-a-glance summary of the published catalogue') and enumerates the exact contents (fresh, aging, stale, reference counts, latest health check time). This clearly distinguishes it from siblings like find_stale or usage_summary.
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 description implies the appropriate use case: when an agent needs a quick overall freshness summary of the catalogue. However, it does not explicitly state when to prefer this over alternatives such as find_stale or find_deteriorating, nor does it mention exclusions.
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.
Each tool targets a distinct workflow—search, detail retrieval, freshness checking, licence enumeration, and citation metadata. The only mild overlap is between get_dataset and get_provenance, both exposing metadata, but their descriptions differentiate full health/freshness detail from citation-ready provenance.
All tool names follow a clear verb_noun pattern in snake_case: find_, get_, and search_ prefixes are used consistently. Minor stylistic variation between find_by_licence and find_stale does not undermine predictability.
Five tools is well-scoped for a dataset catalog server, covering discovery, inspection, health assessment, licence scoping, and citation. No redundant or excessive tools are present.
The core lifecycle is covered: search to find datasets, get_dataset for full detail, find_stale for freshness risk, and get_provenance for citation. A minor gap is the lack of a general list-all or status filter beyond stale, but the domain is narrow enough to work around this.