pharmacogenomics-guidelines-mcp-server

Get guideline coverage

pgx_get_guideline

Read-onlyIdempotent

Retrieve guideline coverage by source ID, exact gene symbol or exact drug name/ID. Default summary pages complete guideline records with exact drugCount/pairCount. view=drugs or pairs requires by=id and pages only that related collection, retaining its guideline descriptor. Ambiguous drug names page candidates for retry with drugId. Follow page.nextOffset; the 24,000-byte soft budget cuts only between complete rows, with oversizedRow for an indivisible exception. Missing coverage is found=false. Consult linked guidelines before clinical use.

Input Schema

Name	Required	Description	Default
`by`	Yes	id requires guidelineId; gene requires geneSymbol; drug requires exactly one exact drugName or drugId. Other selectors must be omitted.
`view`	No	Summary pages guideline descriptors; drugs or pairs requires by=id and pages only that related collection.	summary
`limit`	No	Positive safe-integer row limit; values above 100 are clamped to 100 with a notice (default 25).
`drugId`	No	Exact drugId returned by pgx_search_pairs; blank means unset.
`offset`	No	Zero-based offset; use nextOffset to continue (default 0).
`drugName`	No	Exact case-insensitive source drug name for by=drug; blank means unset.
`geneSymbol`	No	Gene symbol for by=gene; blank means unset.
`guidelineId`	No	Positive source guideline ID from pgx_get_guideline by=gene or by=drug results; no valid ID range is inferred.

Output Schema

Name	Required	Description
`cap`	No	Effective public page limit.
`page`	No	Source pagination metadata.
`view`	No	Selected guideline view.
`drugs`	No	Selected drugs page; omitted in other views.
`error`	No	Present when the call failed. Absent on success.
`found`	No	Whether guideline coverage was found.
`pairs`	No	Selected pairs page; omitted in other views.
`shown`	No	Number of returned rows, equal to page.returned.
`notices`	No	Notices about this result; empty when none apply.
`guidance`	No	Next lookup step when missing or ambiguous; empty when found.
`truncated`	No	Whether more matching rows remain after this page.
`candidates`	No	Paged exact drug-name candidates when resolution is ambiguous; page and shown then refer to candidates.
`guidelines`	No	Paged complete guideline descriptors, or the retained descriptor for a related view.
`provenance`	No	Live source attribution and retrieval details.
`oversizedRow`	No	Whether one complete indivisible row exceeds the soft byte budget.
`clinicalCaveat`	No	Clinical qualification for source guidance.
`effectiveQuery`	No	Normalized guideline selectors and effective page bounds.

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 24, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Adds substantial behavior beyond the readOnly/openWorld/idempotent annotations: pagination via nextOffset, a 24,000-byte soft budget that cuts only between complete rows, and oversizedRow as the indivisible exception. It also discloses that missing coverage returns found=false and advises consulting linked guidelines before clinical use.

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?

The purpose and selectors are front-loaded, and subsequent sentences cover view modes, pagination, size limits, missing results, and a clinical-use caution without filler. The density is appropriate for a parameterized read tool with nuanced pagination behavior.

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?

With an output schema and complete parameter descriptions available, the description still covers the essential operational details an agent needs: selector modes, view constraints, pagination behavior, oversized-row handling, missing-coverage semantics, and a clinical-use warning. Nothing material is missing for correct invocation.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents all parameters. The description still adds useful semantics about the by selector modes, view behavior, and ambiguous drug-name paging with drugId retry, though it does not add much for limit, offset, or guidelineId beyond the schema.

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

Purpose4/5

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

States a specific retrieval action and resource: guideline coverage by source ID, exact gene symbol, or exact drug name/ID. The scope is clear, but the description does not explicitly differentiate this tool from siblings such as pgx_get_recommendations or pgx_search_pairs.

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?

Explains when to use summary versus drugs/pairs views, including the requirement that view=drugs or pairs needs by=id. It also tells the agent how to recover from ambiguous drug names by retrying with drugId, though it does not explicitly compare this tool against sibling tools.

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

All pharmacogenomics-guidelines-mcp-server tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.