check_healthReturn environment and API health. Never returns secrets. No API key required.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
| health | No | Ops health without secrets | |
| api_key | Yes | set or unset — never the raw secret | |
| refusal | No | ||
| version | 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?
Beyond the annotations (readOnlyHint, openWorldHint, etc.), the description adds meaningful behavioral assurances: 'Never returns secrets' and 'No API key required.' These are valuable safety and authentication details not present in the 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?
Two concise sentences front-load the core purpose, with every word contributing value. No redundancy or filler, making it highly efficient.
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 health-check tool with an empty input schema and an existing output schema, the description is complete. It covers environment/API health, safety (no secrets), and authentication requirements, leaving no significant 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?
The tool has zero parameters, so the schema already fully covers parameter semantics. The description adds nothing about parameters, but none are needed. Baseline for no parameters is 4.
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 'Return environment and API health' with a specific verb and resource, distinguishing it from sibling tools like apply_fix and audit_url. No ambiguity about what this tool does.
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?
It provides useful context ('No API key required') but does not explicitly state when to use this tool over alternatives or mention exclusions. The usage context is implied rather than explicit.
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 has significant overlap: audit_url and rescore_url both run the same structural audit, and list_fixes vs apply_fix both generate fix packs (with apply_fix differing only by optional write access). This blurs boundaries and forces agents to rely on subtle wording to choose correctly.
All tool names follow a consistent verb_noun snake_case pattern (apply_fix, audit_url, check_health, get_brief, list_fixes, rescore_url). The verbs are distinct and clearly indicate the action, making the naming predictable and easy to parse.
With 6 tools, the server is well-scoped for its purpose. Each tool covers a specific step in the audit-to-fix workflow without excessive bloat or noticeable omissions.
The core workflow is covered: audit (audit_url/rescore_url), brief (get_brief), and fixes (list_fixes/apply_fix), plus health check. Minor gap: no explicit tool to view detailed individual recommendations or manage applied fixes, but agents can work around this using the available outputs.