Skip to main content
Glama

howlong_clearance

Estimate when a GLP-1/GIP injection is essentially cleared after the last dose, from the SmPC half-life (about five half-lives). Give the drug and the last-dose date. Returns the clear date and whether the basis is the SmPC or an estimate. Informational.

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>",
      "last_dose": "<last_dose>"
    },
    "name": "howlong_clearance"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugYes
last_doseYesDate of the last dose, YYYY-MM-DD

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description does meaningful work: it discloses the calculation basis (SmPC half-life, ~5 half-lives), what is returned (clear date and whether the basis is SmPC or an estimate), and an informational/not-medical-advice caveat. It stops short of noting accuracy limits such as individual pharmacokinetic variation or conditions that invalidate a half-life estimate.

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 short sentences, front-loaded with the estimate and method, then inputs, then return value, then the informational disclaimer. No filler or duplicated phrasing.

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 simple two-parameter read-only estimate with no output schema, the description covers method, inputs, and return shape adequately. Minor gaps remain around the precise definition of 'essentially cleared' and how the estimate differs when SmPC data is unavailable.

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?

The schema already names both parameters and documents last_dose as YYYY-MM-DD; drug is an enum of four products. The description only restates 'the drug and the last-dose date', adding the GLP-1/GIP class context but no per-parameter detail, so this sits at the baseline for 50% coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (estimate) and resource (when a GLP-1/GIP injection is essentially cleared after the last dose), plus the method (SmPC half-life, ~5 half-lives). It does not name or contrast with the sibling howlong_timeline, so differentiation is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: 'Informational' plus 'Give the drug and the last-dose date' tells the agent what inputs to supply but not when this tool is preferable to howlong_timeline or other howlong/supply tools. There are no exclusions or alternatives stated.

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.

Resources