Skip to main content
Glama
Sign In
PubCrawl

PubCrawl

by nickjlamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_uspi

Read-only

Retrieve FDA US Prescribing Information for a drug from openFDA, cited to DailyMed, with structured label sections and paged access for long sections.

Instructions

Get FDA US Prescribing Information (USPI) for a drug from openFDA (cited to DailyMed). Returns structured labelling sections with LOINC codes, verbatim. Long sections are paged: a cut section has truncated: true, total_chars and next_offset — call again with that section and offset to read on. Check drug_name: the best openFDA match may be a different product from the one you meant.

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": {
      "drug": "<drug>"
    },
    "name": "get_uspi"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugYesDrug name to look up (e.g., 'metformin', 'atorvastatin')
offsetNoCharacter offset to start each section from (default 0). To read the rest of a truncated section, call again with sections set to that one section and offset set to its next_offset.
sectionsNoSpecific sections to retrieve (e.g., ['indications', 'adverse reactions', 'contraindications']). Returns all sections if omitted.
max_charsNoMaximum characters returned per section (default 6000). Long sections are returned a page at a time: a cut page has truncated: true, total_chars and next_offset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv2.8.0
    • addedInput schema / properties / max_chars
      Added value: +{
+  "description": "Maximum characters returned per section (default 6000). Long sections are returned a page at a time: a cut page has truncated: true, total_chars and next_offset.",
+  "maximum": 50000,
+  "minimum": 500,
+  "type": "integer"
+}
    • addedInput schema / properties / offset
      Added value: +{
+  "description": "Character offset to start each section from (default 0). To read the rest of a truncated section, call again with sections set to that one section and offset set to its next_offset.",
+  "maximum": 9007199254740991,
+  "minimum": 0,
+  "type": "integer"
+}
  2. First observedv2.5.1

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so safety is covered; the description adds substantive behavior the annotations cannot convey: content is verbatim, sections carry LOINC codes, truncation is signalled per section with total_chars/next_offset, and the top openFDA match may be the wrong product. It omits auth/rate-limit or no-match error behavior.

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?

Four tight sentences, front-loaded with what the tool returns, followed by the paging rule and the matching caveat. No filler, no restatement of the tool name, and each sentence carries operational information.

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?

With no output schema, the description carries the burden of describing returns and does so (structured sections, LOINC codes, verbatim text, truncated/total_chars/next_offset). For a 4-parameter read tool this is nearly complete, with only edge cases such as no-match behavior or result size expectations left unstated.

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 baseline is 3, but the description adds meaning beyond the schema by framing offset/sections as a paging loop and warning that drug_name resolution may return a different product. It does not further clarify max_chars limits or section-name vocabulary beyond what the schema already says.

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 ('Get FDA US Prescribing Information (USPI) for a drug'), names the source (openFDA, cited to DailyMed), and returns a distinguishable artifact (LOINC-coded labelling sections). This clearly separates it from siblings like get_smpc (EU SmPC) or get_trial.

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 actionable guidance for the paging case ('call again with that section and offset to read on') and a verification step ('Check drug_name: the best openFDA match may be a different product'). It does not explicitly route the agent among siblings (e.g. when to prefer get_smpc or compare_labels), which keeps it from a 5.

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