On the Register

sideeffects_list

List the SmPC side effects of a GLP-1/GIP injection (Mounjaro, Wegovy, Ozempic, Saxenda) by frequency band, plus the serious warnings with what to do (999/111/prescriber) and the Yellow Card link. General leaflet information, not a prediction and not triage.

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": "sideeffects_list"
  }
}

Input Schema

Name	Required	Description	Default
`drug`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.3/5.0

Behavior4/5

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

With no annotations supplied, the description carries the disclosure burden and does well: it states the output is organized by frequency band, includes serious warnings with escalation guidance (999/111/prescriber) and a Yellow Card link, and frames the content as general leaflet information rather than individualized advice. It does not explicitly say the call is read-only or whether results vary by drug, but the listing verb makes the read-only nature apparent.

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 the verb and payload, followed by a short scope disclaimer. Dense but every clause adds information; the '999/111/prescriber' shorthand is compact without being ambiguous in a UK context.

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?

A one-parameter lookup tool with no output schema, so the description must sketch the return shape, and it does: frequency bands, serious warnings, actions, and an external reporting link. Little else an agent would need in order to call it correctly is missing.

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 0%, so the description must compensate, and it does by enumerating the four accepted brands (Mounjaro, Wegovy, Ozempic, Saxenda), which map onto the lowercase enum values. No further detail is needed for a single enumerated parameter.

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?

Specific verb (List) plus a precisely scoped resource: SmPC side effects by frequency band for four named GLP-1/GIP injections. It also names the extra payload (serious warnings, action guidance, Yellow Card link), so an agent can distinguish it from every sibling, none of which covers side effects.

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 closing clause supplies an explicit exclusion: 'not a prediction and not triage,' which tells the agent when this output must not be used. No alternative sibling is named, but no sibling performs this function, so the absence of routing is minor.

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

All On the Register tools Inspect

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

Need Help?