Skip to main content
Glama
Open Drug Data MCP
by knorby

Ping the server

drugdata_ping
Read-onlyIdempotent

Verify the server is running and confirm which drug data sources and API keys are configured before searching. Requires no credentials or network.

Instructions

Check that the server is running and see which data sources this process will use. Reports the server name and version, each source's adapter id and whether it is enabled, and whether its API key is configured (never the key itself). Needs no credentials and no network — use it to verify connectivity before searching.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "drugdata_ping"
  }
}

Input Schema

NameRequiredDescriptionDefault
messageNoOptional message to echo back in the text response. Omit for a plain 'pong'.

Output Schema

NameRequiredDescriptionDefault
okYesAlways true — the server answered.
serverYesServer identity.
sourcesYesEvery source, in the server's fixed order.
referenceSourcesYesKey situation for the NLM reference sources.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover read-only/idempotent/non-destructive/closed-world, but the description adds real behavioral facts: no credentials required, no network access required, and that API keys are never returned. The enumeration of reported fields partially restates the output schema, but the secret-safety and no-auth guarantees are genuinely additive. It stops short of describing error/failure behavior when a source is misconfigured.

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 compact sentences, front-loaded with purpose and followed by what is reported and the intended use. Every clause carries information; nothing is padding.

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?

For a zero-required-parameter health-check tool with rich annotations and an output schema, the description covers purpose, prerequisites, sensitivity guarantees, and intended usage. Nothing an agent needs in order to call this correctly is missing.

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

Parameters3/5

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

Schema coverage is 100% and the single optional 'message' parameter is fully documented in the schema (including the 'pong' default behavior for omission). The description never mentions the echo parameter, so it adds no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('Check that the server is running') plus the scope of what it reports: server name/version, each source's adapter id, enabled flag, and API-key-configured status. This is clearly distinguishable from the sibling search/get tools, which operate on drug data rather than process health.

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?

Gives an explicit when-to-use: 'use it to verify connectivity before searching,' and notes prerequisites ('Needs no credentials and no network'). It doesn't name a specific sibling alternative, but for a health-check tool there is no meaningful alternative to route against, so the context is sufficient.

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