Skip to main content
Glama

rx_health

Read-onlyIdempotent

Check server connectivity before running drug shortage queries. A zero-argument health check that confirms the server is reachable.

Instructions

Confirm the rx_shortage_mcp server is running and reachable.

A zero-argument connectivity check. Use it to verify the server is live
before running the shortage → alternatives → cascade-check chain.

Returns:
    HealthStatus: {
        "status": str,      # "ok" when healthy
        "server": str,      # "rx_shortage_mcp"
        "version": str,     # package version, e.g. "0.1.0"
        "next_step": str    # what to call next
    }

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
serverYes
statusYes
versionYes
next_stepYes
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. Description adds return structure fields (status, server, version, next_step) and confirms zero arguments, adding value beyond annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs: first states purpose, second gives usage guidance and return fields. No redundant information, every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given zero parameters, full annotation coverage, and described output schema, the description is fully adequate. It explains purpose, usage, and return format completely.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

No parameters exist; schema coverage 100%. Description confirms 'zero-argument' and does not need to add parameter details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Description clearly states it is a connectivity check to confirm server is live, with explicit 'zero-argument connectivity check'. Distinguishes from siblings by positioning as prerequisite before chain.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says to use to verify server is live before the chain shortage → alternatives → cascade-check. Does not mention exclusions but context makes usage clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Travis-Clement-Dev/rx-shortage-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server