Skip to main content
Glama

Mhra Alert Detail

mhra_alert_detail
Read-onlyIdempotent

Full text of one MHRA safety alert or recall from GOV.UK, given the alert URL or path returned by mhra_safety_alerts. Returns the complete notice as plain text, for a medicines recall that means the affected batch numbers and expiry dates, the marketing authorisation (PL) number, the active ingredient, the recall class and the action the recipient must take, plus the issue date, alert category and any withdrawal notice.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "/drug-device-alerts/class-2-medicines-recall-zentiva-pharma-uk-limited-fingolimod-zentiva-0-dot-5-mg-capsules-el-26-a-slash-37"
    },
    "name": "mhra_alert_detail"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe alert URL or GOV.UK path, e.g. "/drug-device-alerts/class-2-medicines-recall-zentiva-pharma-uk-limited-fingolimod-zentiva-0-dot-5-mg-capsules-el-26-a-slash-37" or the full https://www.gov.uk/... form.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered; the description goes further by describing output shape and content — plain text, batch numbers and expiry dates, PL number, active ingredient, recall class, required action, issue date, category and withdrawal notices. It does not mention what happens with a malformed or non-alert URL, which is the main behavioral gap.

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?

Two sentences, front-loaded with what the tool does and followed by what comes back; no filler. The return-content enumeration is long but each item (batch numbers, PL number, recall class, action) is substantive rather than redundant.

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 one-parameter read tool with full annotation coverage and no output schema, the description carries the return-value burden well by enumerating what the plain text contains. The only shortfall is no note on error/failure behavior for URLs that are not valid MHRA alerts.

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?

Schema coverage is 100% and the single 'url' parameter is fully documented with examples in the schema, so the baseline is 3. The description adds a small amount of meaning by stating the URL comes from mhra_safety_alerts, but contributes nothing on form, normalization, or invalid-path handling beyond the schema.

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?

Names a specific verb and resource ('Full text of one MHRA safety alert or recall from GOV.UK') and explicitly distinguishes itself from the sibling listing tool by tying its input to the URL/path 'returned by mhra_safety_alerts'. An agent can tell immediately this is the detail-fetch counterpart to the list 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 gives clear usage context: call this with a URL/path obtained from mhra_safety_alerts, which chains the two tools correctly. It does not state exclusions (e.g. when to prefer mhra_drug_safety_update or recall instead) or note that a full URL vs. path are interchangeable, so it stops short of explicit when-not guidance.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.