Govparse Government Data Gateway

trials_trials_search

Which companies are running clinical trials, and at what stage? Search ClinicalTrials.gov interventional industry-sponsored studies by lead sponsor, phase, status, condition, intervention type, a US state with a site, first-posted date (since), start date, or completion date. Returns the sponsor (entity-resolved where possible), phase, status, conditions, enrollment, and dates — a developer target list for CRO, trial-software, and commercial-ops sellers. ClinicalTrials.gov public records. [price: $0.05/row]

Input Schema

TableJSON Schema

Name	Required	Description
`sort`	No	first_posted_date \| start_date \| completion_date \| last_update_date :asc\|:desc. Default first_posted_date:desc.
`limit`	No	Max rows (default 25, cap 100).
`phase`	No	Trial phase(s), CSV (PHASE1 \| PHASE2 \| PHASE3 \| PHASE4 \| EARLY_PHASE1).
`since`	No	First posted to the registry on/after this date (YYYY-MM-DD).
`state`	No	Has a trial site in these US state code(s), CSV.
`offset`	No	Rows to skip.
`status`	No	Overall status, CSV (RECRUITING \| COMPLETED \| TERMINATED \| ...).
`sponsor`	No	Lead sponsor company — suffix/punctuation-insensitive.
`condition`	No	Indication / condition fragment.
`entity_id`	No	Resolved sponsor employer entity UUID (pivots to business360).
`started_after`	No	Study start on/after this date (YYYY-MM-DD).
`completed_after`	No	Study completion on/after this date (YYYY-MM-DD).
`intervention_type`	No	Intervention type, CSV (DRUG \| DEVICE \| BIOLOGICAL \| ...).

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

AddedJul 24, 2026

TDQS

B3.1/5.0

Behavior3/5

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

With no annotations provided, the description must convey behavioral traits. It mentions the data source (ClinicalTrials.gov public records), pricing ($0.05/row), and entity resolution for sponsors. However, it does not discuss pagination, error handling, or rate limits, leaving some behavioral gaps.

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?

The description is a single paragraph that efficiently front-loads the purpose and lists filters, output, target audience, source, and pricing. While it is not overly long, breaking it into bullet points could improve readability.

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?

Given 13 parameters and no output schema, the description covers the output fields, data source, pricing, and target use case. It lacks details on pagination or result interpretation, but overall provides sufficient context for an agent to understand the tool's capabilities.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema already describes all 13 parameters in detail (100% coverage). The description adds little beyond listing filter categories in prose; it does not provide format clarifications or usage tips not already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool searches ClinicalTrials.gov for interventional industry-sponsored studies, listing specific filters and output fields. It distinguishes itself from a generic search by focusing on sponsor and stage, but does not explicitly differentiate from the sibling 'trials_sites_search' for site-specific queries.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'trials_sites_search' or other sibling search tools. The description lists filters but lacks context on exclusions or when not to use this tool.

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

All Govparse Government Data Gateway tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.2/5.0

Disambiguation5/5

Each tool targets a distinct domain and specific action (e.g., FDA approvals vs clearances vs recalls; firmstanding business360 dossier vs search vs screen). Even overlapping concepts like 'business360' vs 'business360_lookup' are distinguished by input (UUID vs name+state). No two tools appear to do the same thing.

Naming Consistency5/5

All tools use a consistent lowercase snake_case pattern with domain prefix (e.g., fda_*, firmstanding_*, fmcsa_*, govcon_*). Action words (search, lookup, screen, feed, stats) follow predictable usage. The naming is uniform and easy to parse.

Tool Count4/5

38 tools is on the higher end but appropriate for a comprehensive government data gateway spanning multiple agencies and datasets. Each domain has a reasonable number of tools (e.g., FMCSA: 7, OFLC: 6). Could potentially be trimmed slightly, but overall well-scoped for the stated purpose.

Completeness5/5

The tool surface covers the major government data sources comprehensively: FDA (approvals, clearances, recalls), FMCSA (carrier census, safety, insurance, etc.), FSIS, DOJ/OFLC, OSHA/EPA/DOL enforcement, SEC insider filings, clinical trials, VA facilities/opportunities/vendors, and federal contracting. No obvious gaps for the stated gateway purpose.

Resources

Need Help?