Skip to main content
Glama
Sign In

AgingResearch.News

by news.agingresearch
OverviewDiscussionsAdmin

List clinical trials

list_trials
Read-onlyIdempotent

Use this when the user asks about clinical trials on aging or an age-related condition: what is recruiting, what changed lately, which trials test a drug, which companies run them. Trials that bear on human aging, newest registry update first, with phase, status, sponsor, size, conditions, interventions and the latest change. Read one with get_trial.

Input Schema

NameRequiredDescriptionDefault
qNoWords that must all appear in the trial's titles, conditions, interventions, keywords or sponsor (case-insensitive).
focusNoThe trial's main connection to aging (see `focus`).
limitNoResults per page.
phaseNoPhase: `1` (early phase 1 and phase 1), `2`, `3`, `4`, or `none` for studies with no phase.
sinceNoOnly trials the registry updated on or after this date (YYYY-MM-DD).
cursorNoFrom the last page's `pagination.next_cursor`; keep the other arguments the same.
statusNoRecruitment status: `recruiting` (recruiting, not yet recruiting or by invitation), `active` (active, not recruiting), `completed`, or `stopped` (terminated, withdrawn or suspended).
industryNo`true` for trials whose lead sponsor is a company, `false` for the rest. Omit for both.
min_relevanceNoLowest aging-relevance score to include (0 to 3, see `relevance`). Default 1.8, the trials about aging.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • changedInput schema / properties / cursor / description
      Previous value: -"Opaque cursor from `pagination.next_cursor` of the previous page. Keep the other parameters the same."New value: +"From the last page's `pagination.next_cursor`; keep the other arguments the same."
    • removedInput schema / properties / focus / examples
      Removed value: -[
-  [
-    "intervention"
-  ]
-]
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page, 1 to 25."New value: +"Results per page."
    • removedInput schema / properties / phase / examples
      Removed value: -[
-  [
-    "2",
-    "3"
-  ]
-]
    • removedInput schema / properties / status / examples
      Removed value: -[
-  [
-    "recruiting"
-  ]
-]
  2. Changed1 schema field changed
    • changedInput schema / properties / min_relevance / description
      Previous value: -"Lowest aging-relevance score to include (0 to 3, see `relevance`). Default 1.8, the trials /trials shows."New value: +"Lowest aging-relevance score to include (0 to 3, see `relevance`). Default 1.8, the trials about aging."
  3. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive/closed-world, so the safety profile is covered. The description adds ordering semantics ('newest registry update first') and the returned field set (phase, status, sponsor, size, conditions, interventions, latest change), which the agent cannot infer from annotations. It stops short of describing pagination behavior beyond the cursor parameter itself.

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?

Two sentences, both front-loaded: the trigger and scope come first, then the sort order and result fields, then the handoff to get_trial. Every clause earns its place by mapping to a filter or a returned field.

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?

With no output schema, the description compensates by naming what each result contains, and the sort order is stated. All nine parameters, including the relevance floor and cursor paging contract, are documented in the schema, so nothing an agent needs to call this 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 coverage is 100%, so the baseline is 3, and the description meaningfully raises it by mapping user intents to filters: 'what changed lately' points to since, 'which trials test a drug' to q/intervention, and 'which companies run them' to industry. It does not add syntax or format detail beyond what the schema already documents.

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?

States a specific verb (list) and resource (clinical trials) with an explicit scope constraint: trials bearing on human aging or age-related conditions. It also names the read-one sibling (get_trial), so an agent can distinguish listing from fetching without opening either schema.

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

Usage Guidelines5/5

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

Opens with an explicit trigger ('Use this when the user asks about...') and enumerates the question shapes it serves: recruiting, recent changes, drug-testing, company sponsors. It closes by routing single-record lookups to get_trial, giving a concrete alternative and the condition that selects it.

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

All AgingResearch.News 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