statusReport how fresh every enabled curated service is: when each source last succeeded, last failed, and whether it is stale.
| 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?
The readOnlyHint annotation is present and the description ('Report') aligns with read-only behavior. No additional behavioral details are needed for a simple status query.
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?
Single sentence, concise and directly to the point. No extraneous words or vague phrasing.
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?
Description adequately conveys the purpose and the kind of information returned (freshness, last success/failure, staleness). Output schema is indicated as present, so not detailing structure here is acceptable.
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?
No parameters exist, and schema coverage is 100% (empty schema). The description adds no parameter information because none are needed.
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?
Clearly states the action (Report) and the specific resource (freshness of every enabled curated service), including details about last success, last failure, and staleness. Distinct from all sibling tools which are get/search/list operations.
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?
Description explains what the tool does but provides no explicit guidance on when to use it versus alternatives. However, the purpose is self-evident as a status check, so it doesn't create confusion.
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.
Every tool has a unique purpose, and the descriptions are detailed enough to clearly distinguish between search, list, get, and specific operations across domains. No two tools overlap in function.
Domain tools follow a consistent '<domain>_<verb>_<noun>' pattern, but gateway-level tools like 'call_tool', 'find_capability', 'inspect_tool', 'search_services', and 'status' lack the prefix, introducing a minor inconsistency. Overall still readable and predictable.
With 35 tools, the count exceeds the typical 3–15 range, but this is a gateway aggregating multiple distinct domains (holidays, laws, opendata, recalls, etc.), making the larger set justified. The count feels appropriate for the server's purpose.
Each domain offers a full set of operations: search, list, get, and domain-specific actions (like count_business_days or get_document_changes). Gateway meta-tools cover discovery, inspection, and invocation, leaving no obvious gaps.