Skip to main content
Glama

search_trials_nct_ids_only

Lightweight search returning only NCT IDs and minimal metadata for discovery.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
termsNoGeneral search terms
sponsorsNoSponsor organizations to search for
conditionsNoMedical conditions to search for
max_studiesNoMaximum number of studies to return
interventionsNoInterventions/treatments to search for

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed20 schema fields changed
    • addedInput schema / $schema
      Added value: +"http://json-schema.org/draft-07/schema#"
    • removedInput schema / properties / conditions / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / conditions / default
      Removed value: -null
    • addedInput schema / properties / conditions / items
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / conditions / type
      Added value: +"array"
    • removedInput schema / properties / interventions / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / interventions / default
      Removed value: -null
    • addedInput schema / properties / interventions / items
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / interventions / type
      Added value: +"array"
    • changedInput schema / properties / max_studies / description
      Previous value: -"Maximum number of studies to return (optimized for discovery)"New value: +"Maximum number of studies to return"
    • changedInput schema / properties / max_studies / type
      Previous value: -"integer"New value: +"number"
    • removedInput schema / properties / sponsors / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / sponsors / default
      Removed value: -null
    • addedInput schema / properties / sponsors / items
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / sponsors / type
      Added value: +"array"
    • removedInput schema / properties / terms / anyOf
      Removed value: -[
      -  {
      -    "items": {
      -      "type": "string"
      -    },
      -    "type": "array"
      -  },
      -  {
      -    "type": "null"
      -  }
      -]
    • removedInput schema / properties / terms / default
      Removed value: -null
    • addedInput schema / properties / terms / items
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / terms / type
      Added value: +"array"
    • changedOutput schema / (root)
      Previous value: -{
      -  "additionalProperties": true,
      -  "type": "object"
      -}New value: +null
  2. First observed

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the full burden. It discloses the limited return format ('only NCT IDs and minimal metadata') and lightweight nature, but omits safety characteristics (read-only status), rate limits, or specific metadata fields returned.

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?

Single sentence of 9 words with zero waste. Front-loaded with the key differentiator 'Lightweight' immediately signaling performance characteristics, followed by precise return value constraints.

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?

Adequately covers the tool's core function and return format given the straightforward 5-parameter schema with complete coverage. Could improve by noting that all parameters are optional (0 required) or explicitly contrasting with the full-detail sibling tools in this crowded search namespace.

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% (all 5 parameters documented), establishing a baseline of 3. The description provides no additional parameter semantics, but none are needed given the comprehensive schema documentation.

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 provides a specific verb ('search'), clear resource scope ('NCT IDs'), and distinguishes from siblings through 'lightweight' and 'only NCT IDs'—clearly positioning it as a minimal alternative to comprehensive tools like search_trials_combined or get_trial_details.

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

Usage Guidelines3/5

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

Includes implied usage context ('for discovery') but lacks explicit when-to-use guidance versus the numerous sibling search tools (e.g., 'use this instead of search_trials_combined when you only need identifiers').

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