Skip to main content
Glama
Sign In
openpgx

openpgx

Official
by open-pgx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Compare Medications

compare_medications
Read-onlyIdempotent

Compare two medications head-to-head to determine which is more suitable for your genetic profile. Accepts brand and generic names.

Instructions

Compare two medications head-to-head based on your genetic profile. Supports brand names.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "drug1": "<drug1>",
      "drug2": "<drug2>"
    },
    "name": "compare_medications"
  }
}

Input Schema

NameRequiredDescriptionDefault
drug1YesFirst medication (generic or brand)
drug2YesSecond medication (generic or brand)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the tool's safe read nature is clear. The description adds critical context that the comparison is personalized (based on genetic profile), which is beyond annotations. No contradictions.

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 sentences with no extraneous information. The purpose is front-loaded and every word is informative. Ideal conciseness.

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

Completeness3/5

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

With no output schema, the description does not explain the return format (e.g., side-by-side comparison, scores, or textual analysis). Annotations cover safety but not result structure. For a comparison tool, some indication of output would improve completeness.

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?

Both parameters have descriptions in the schema (e.g., 'First medication (generic or brand)'). The description reinforces 'Supports brand names' but adds no new semantics beyond the schema. With 100% schema coverage, baseline 3 is appropriate.

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?

The description clearly states the tool compares two medications head-to-head using genetic profile, with specific verb 'compare' and resource 'medications'. It also notes support for brand names, which distinguishes it from siblings like check_medication that likely handle single drugs.

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

Usage Guidelines2/5

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

No explicit guidance on when to use this tool over siblings such as check_medication or search_drug_pgx. The description implies comparison use case but fails to specify exclusions or prerequisites like requiring a loaded genetic profile.

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

Deploy Server

Other Tools