Skip to main content
Glama
Sign In

Eu Ctis

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Ctis Trials For Medicine

ctis_trials_for_medicine
Read-onlyIdempotent

Every EU/EEA clinical trial involving a named medicine or active substance, from the EU Clinical Trials Information System, newest authorisation first. Splits the result by trial status so it is clear how many are still recruiting versus ended, and lists sponsors and member states. Answers "what is running in Europe for this drug".

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": {
      "limit": 3,
      "medicine": "semaglutide"
    },
    "name": "ctis_trials_for_medicine"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoTrials to return, 1-100 (default 25)
countryNoRestrict to these member states
medicineYesMedicine, brand or active substance name, e.g. "semaglutide"
recruiting_onlyNoOnly trials currently authorised or recruiting

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive hints. The description adds valuable behavioral detail beyond those hints: it splits results by trial status, lists sponsors and member states, and specifies newest-authorisation-first ordering, giving the agent a clear picture of the response shape without an output schema.

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?

The description is three sentences with no filler. It front-loads the core scope and resource, then adds the distinguishing behavioral details (status split, sponsors, member states) and concludes with a concrete user question the tool answers.

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

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the read-only, idempotent annotations and complete parameter schema, the description covers what the agent needs to know: what data is returned, how it is organized, and what question it answers. Without an output schema, the description still adequately describes the response composition (statuses, sponsors, member states) and ordering.

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 description coverage is 100%, so the schema fully documents all four parameters. The description adds some semantic context by noting that results cover every EU/EEA trial for a medicine and that status splits are included, which loosely relates to recruiting_only, but it does not substantially extend the meaning beyond what the input schema already provides.

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 states a specific verb and resource: it returns EU/EEA clinical trials for a named medicine from the EU Clinical Trials Information System, ordered newest authorisation first. It clearly differentiates itself from siblings like ctis_recent_authorisations and ctis_search_trials by focusing on drug-specific trial enumeration with status breakdowns.

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 explicitly frames when to use it: answering 'what is running in Europe for this drug'. It provides clear context for drug-specific queries but does not explicitly mention when not to use it or name alternative sibling tools, so it stops short of full routing guidance.

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

All Eu Ctis toolsInspect
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