Skip to main content
Glama

Midgard Finance drug data

Get weight-loss trajectory

get_trajectory
Read-only

The digitised weight-loss curve for a drug: week-by-week points, plus per-dose series.

Returned with endpoint_pct and its estimand alongside the curve, because the endpoint marker and the last plotted point are different quantities and the curve alone does not say which one a reader is looking at.

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_trajectory"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, so the safety profile is covered. The description adds genuinely useful return semantics: the curve is returned with endpoint_pct and its estimand, and it flags the important distinction between the endpoint marker and the last plotted point.

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 compact sentences, front-loaded with the resource and followed by the return-value caveat. The second sentence is slightly dense but every clause adds meaning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/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 no output schema, the description covers the return shape reasonably well but leaves the parameter input semantics unexplained. Adequate, with a clear gap around how to identify the drug.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single required `drug` parameter, so the description must carry the burden — but it never explains what form `drug` takes (name, ID, slug) or how matching works. This is a real gap for an agent trying to call it.

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?

The description states a specific resource — the digitised weight-loss curve for a drug, week-by-week points plus per-dose series — so an agent knows what it retrieves. It doesn't explicitly distinguish itself from siblings like compare_efficacy, but the resource is concrete enough to be unambiguous in context.

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

Usage Guidelines2/5

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

There is no statement of when to use this tool versus compare_efficacy or get_drug, and no exclusions or prerequisites. Usage is only implied by the domain vocabulary.

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