Skip to main content
Glama
Sign In
PubCrawl

PubCrawl

by nickjlamb
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

get_smpc

Read-only

Retrieve UK/EU Summary of Product Characteristics (SmPC) for a drug from eMC, returning structured labelling sections verbatim with paging for long sections.

Instructions

Get UK/EU Summary of Product Characteristics (SmPC) for a drug from eMC (medicines.org.uk). Returns structured labelling sections, 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 eMC match may be a different product or formulation 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_smpc"
  }
}

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 — accepts numbers like '4.1' or names like 'indications'. 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.7/5.0
Behavior5/5

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

Annotations already declare read-only, open-world, non-destructive behavior, but the description adds important context beyond them: sections are returned verbatim, long sections are paged with truncated: true, total_chars, and next_offset, and the caller must repeat the call with that section and offset. It also discloses the practical risk that the best drug-name match may be a different product or formulation.

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 the source and return format, followed by pagination mechanics and the drug-name match warning. Every sentence contributes useful information with no filler.

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?

There is no output schema, but the description sufficiently explains the return structure: structured labelling sections, verbatim content, truncation fields, and how to continue reading. For a read-only retrieval tool with full schema coverage, an agent has enough information to invoke it and page through long sections correctly.

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 baseline is 3, but the description adds workflow meaning for sections/offset/max_chars by explaining the paging loop and continuation behavior. It also adds a drug_name caveat not present in the schema, raising it above the baseline.

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 UK/EU SmPC for a drug from eMC, returning structured labelling sections. By naming UK/EU SmPC and eMC, it distinguishes the tool from sibling get_uspi, which covers US labelling, even without naming that sibling explicitly.

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?

Clearly scopes usage to UK/EU SmPC retrieval and warns to check drug_name because the best eMC match may be a different product or formulation. It lacks explicit when-not guidance or direct pointers to sibling alternatives such as resolve_drug_name or compare_labels, so it is strong but not complete.

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