Skip to main content
Glama

Clinicaltables

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Drugs

drugs
Read-onlyIdempotent

"Drug name lookup" / "find prescription [X]" / "medication autocomplete" / "RxCUI for [drug]" / "what does [pill] treat" / "available strengths for [drug]" — search RxTerms (NLM prescribing-vocabulary derived from RxNorm, ~22k drug names with route/strength). Returns names like "Aspirin (Chewable)", "Lisinopril (Oral Pill)". Use for prescription entry, drug name autocomplete, or as a stepping-stone to RxNorm RxCUI lookups. Pass ef="STRENGTHS_AND_FORMS,RXCUIS" to include dosage strengths and RxNorm IDs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
dfNoComma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name.
efNoComma-separated extra fields to include per match. Known fields: STRENGTHS_AND_FORMS,RXCUIS,DISPLAY_NAME_SYNONYM,IS_RETIRED.
countNoMaximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing.
termsYesSearch query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: "aspirin".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "count": 3,
+    "terms": "aspirin"
+  }
+]
  2. Changed7 schema fields changed
    • addedInput schema / properties / count / default
      Added value: +7
    • addedInput schema / properties / count / description
      Added value: +"Maximum matches to return. Default 7, max 500. Use 1–3 for typeahead UX, 20–50 for browsing."
    • addedInput schema / properties / count / maximum
      Added value: +500
    • addedInput schema / properties / count / minimum
      Added value: +1
    • addedInput schema / properties / df / description
      Added value: +"Comma-separated display fields to use in the `displays` array. Default varies per table; usually the canonical name."
    • addedInput schema / properties / ef / description
      Added value: +"Comma-separated extra fields to include per match. Known fields: STRENGTHS_AND_FORMS,RXCUIS,DISPLAY_NAME_SYNONYM,IS_RETIRED."
    • addedInput schema / properties / terms / description
      Added value: +"Search query — prefix/contains match against canonical names. Whitespace-split into AND tokens. Example: \"aspirin\"."
  3. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable context beyond annotations: it specifies the data source (NLM RxTerms, ~22k names), the output format (route/strength in parentheses), and the effect of the ef parameter. No contradiction with annotations.

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

Conciseness4/5

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

The description is front-loaded with query examples and use cases, then details the source and output. Each segment serves a purpose (examples, source, output format, usage, ef hint). It is dense but not bloated; every sentence earns its place, though it is slightly longer than minimal.

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

Completeness4/5

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

For a search tool with 4 parameters, 100% schema coverage, and rich annotations, the description fills the remaining gaps: it explains the return format (names like 'Aspirin (Chewable)') and suggests a typical ef combination. It does not discuss error behavior or edge cases, but these are minor for a read-only lookup with no output schema.

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 description coverage is 100%, with each parameter already explained (e.g., 'terms — prefix/contains match', 'count — max 500'). The description adds extra semantic value by showing a concrete ef value ('STRENGTHS_AND_FORMS,RXCUIS') and by describing result names, which supplements the schema's structured definitions.

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 opens with a list of explicit query phrasings ('Drug name lookup', 'find prescription [X]', etc.) that unambiguously state the resource (RxTerms) and the verb (search/lookup). It also gives concrete output examples ('Aspirin (Chewable)') and mentions the tool's role as a stepping-stone to RxCUI lookups, which differentiates it from any sibling tool.

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?

The description clearly states when to use it: 'Use for prescription entry, drug name autocomplete, or as a stepping-stone to RxNorm RxCUI lookups.' It provides context but does not explicitly name alternatives or exclusions. Given the sibling list contains no other drug-specific tool, this is sufficient guidance.

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

All Clinicaltables toolsInspect
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.

Resources