Skip to main content
Glama

Midgard Finance drug data

List latest news

list_news
Read-only

The latest news the site's hubs print, newest first, with date, headline, source and page.

Use it for "what is new" and "latest announcement" questions. It holds the eight newest items of each hub: obesity, Novo Nordisk and Eli Lilly. company matches the hub (Novo Nordisk, Eli Lilly) or the drug's sponsor, drug a drug or brand in the item or its headline, query a word in the headline (MASH, approval). kind on a Novo hub item says what it is (clinical, regulatory, corporate, results, competitor: a rival's event that bears on Novo). An event older than a hub's eight newest is not here: say so rather than guess. A headline's efficacy figure is on the estimand the headline names, if any, and is not comparable with one on another.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "list_news"
  }
}

Input Schema

NameRequiredDescriptionDefault
drugNo
limitNo
queryNo
companyNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint false, openWorldHint false), yet the description adds real behavioral context: the eight-item-per-hub coverage ceiling, the instruction to disclose rather than fabricate when coverage is exceeded, and the caveat that efficacy figures sit on differing estimands and are not comparable. That is genuine added value beyond the annotations.

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?

It is front-loaded with purpose and usage before parameter semantics and caveats, and nearly every clause carries information. The second paragraph is dense and runs long, and the `kind` clause reads ambiguously against a schema that has no `kind` parameter.

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?

With no output schema, the description usefully enumerates returned fields and the coverage limitation of the underlying data. The unexplained `limit` parameter and the ambiguous `kind` reference keep it from being fully complete for an agent that needs to control result size.

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 carry semantics, and it does for three of four parameters: `company` matches the hub or the drug's sponsor, `drug` a drug or brand in the item or headline, `query` a word in the headline. `limit` is never explained, and the description's "eight newest items of each hub" sits oddly against the schema's limit default of 10, leaving a small inconsistency.

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?

The description gives a specific verb and resource ("the latest news the site's hubs print"), the sort order ("newest first"), and the returned fields ("date, headline, source and page"). It also names the concrete hubs (obesity, Novo Nordisk, Eli Lilly), so an agent can distinguish this from siblings such as list_catalysts or get_trial without opening a schema.

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?

It states the question shapes it serves: "what is new" and "latest announcement". It also gives a clear when-not condition — an event older than a hub's eight newest items is not available, and the agent should say so rather than guess. No sibling tool is named as an alternative, which is the only gap.

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