Skip to main content
Glama
Sign In

AgingResearch.News

by news.agingresearch
OverviewDiscussionsAdmin

List drug and therapy programs

list_assets
Read-onlyIdempotent

Use this when the user asks which drugs or therapies are in development against a target, mechanism, hallmark of aging or age-related disease, who develops them and how far each has got. Drug and therapy programs, furthest stage first, with developers, partners, code names, modality, targets, mechanism, indications with stages and lifespan evidence. Read one with get_asset; count them with count_pipeline. A plan that includes drug and therapy programs reads every record in full; others read an outline, as on the site.

Input Schema

NameRequiredDescriptionDefault
qNoLetters and digits in any of the asset's names or code names (`UBX1325` matches UBX-1325).
kindNo`any` for all; counts default to program.
limitNoResults per page.
stageNoStage: with `indication`, the stage for that indication; otherwise the asset's furthest stage.
cursorNoFrom the last page's `pagination.next_cursor`; keep the other arguments the same.
targetNoA target: a gene symbol or key (`GLP1R`, `bcl2l1`) or a process key (`mtor`, `cellular-senescence`).
countryNoThe developer's country, ISO 3166 alpha-2 (`US`, `GB`, `CH`).
hallmarkNoA hallmark of aging the asset acts on.
modalityNoThe kind of therapy (see `modality`).
mechanismNoWords that must all appear in the asset's mechanism line (case-insensitive).
indicationNoA disease, by name or entity key (`idiopathic pulmonary fibrosis`, `alzheimer-disease`).
organisationNoAn organization key: the assets it develops, partners on or licensed out.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / kind
      Added value: +{
+  "description": "`any` for all; counts default to program.",
+  "enum": [
+    "program",
+    "repurposing",
+    "research",
+    "any"
+  ],
+  "type": "string"
+}
  2. 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 / hallmark / examples
      Removed value: -[
-  "cellular-senescence"
-]
    • changedInput schema / properties / limit / description
      Previous value: -"Results per page, 1 to 25."New value: +"Results per page."
    • removedInput schema / properties / modality / examples
      Removed value: -[
-  "small_molecule"
-]
    • removedInput schema / properties / stage / examples
      Removed value: -[
-  "phase2"
-]
  3. Changed1 schema field changed
    • changedInput schema / properties / organisation / description
      Previous value: -"An organisation key: the assets it develops, partners on or licensed out."New value: +"An organization key: the assets it develops, partners on or licensed out."
  4. First observed

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 (readOnly, idempotent, non-destructive), and the description adds sort order ('furthest stage first') plus the returned field set. The line about a plan 'reads every record in full; others read an outline' discloses a real result-shape quirk, though it is worded vaguely enough that the agent may not be certain how it applies.

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?

Three sentences, front-loaded with the triggering user intent, then results, then routing. The inventory of returned fields is long but functional; no sentence is pure filler.

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 12 optional parameters and no output schema, the description compensates by listing what comes back and in what order. Coverage is good, though the 'reads every record in full' clause could be clearer about its practical effect on the response.

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% with four enums documented inline, so the schema carries the parameter burden. The description adds no filter syntax, combination behavior, or default rules beyond what the schema already states, which is the baseline case for a fully documented schema.

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 and resource ('list' + 'drug and therapy programs') and enumerates the exact user question it answers (what's in development against a target, mechanism, hallmark or disease, and who develops it). The title and first sentence together make it unmistakable next to siblings like get_asset or count_pipeline.

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?

Explicitly names the alternative tools and when to use them: 'Read one with get_asset; count them with count_pipeline.' That is a direct when/when-not routing rule an agent can act on without opening either schema.

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