Skip to main content
Glama

Antigravity x402 & MCP Gateway

fetch_biotech_and_gov_contracts

[0.008000 USDC via x402] Queries ClinicalTrials.gov API v2 for phase, status, sponsor, conditions, and primary completion dates alongside USASpending.gov API v2 prime federal contract awards sorted by exact Decimal USD obligation amount.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "fetch_biotech_and_gov_contracts"
  }
}

Input Schema

NameRequiredDescriptionDefault
modeNoData source selector: 'both' (default), 'clinical_trials', or 'federal_contracts'.
limitNoMaximum records per source to return (1 to 10, default 5).
queryYesCompany, drug/therapy, pathogen, or technology keyword (e.g., 'Pfizer', 'GLP-1', 'Palantir').
x402_payment_signatureNoOptional base64 x402 PAYMENT-SIGNATURE header token (0.008000 USDC on Base eip155:8453 or Polygon eip155:137). Omit to receive the live x402 quote.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses the 0.008000 USDC x402 cost and the fact that contracts are sorted by exact Decimal USD obligation amount, which are real behavioral traits. However, it omits what happens on unpaid/failed x402 calls, whether billing recurs per call, rate limits, and the shape of returned records.

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?

A single dense sentence with the price bracket front-loaded, so the cost is the first thing an agent sees. Every clause carries information, though the two-source construction in one sentence is slightly heavy and could be split for faster scanning.

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?

For a 4-parameter tool with no output schema and no annotations, the description covers the core: both data sources, the priced/paid access model, and result ordering. Remaining gaps are the return-record structure and payment-failure behavior, which a caller would want before spending USDC.

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 schema already documents all four parameters in detail; the baseline would be 3. The description adds marginal value by mapping the domain fields (phase, status, sponsor, conditions, completion dates) to the clinical-trial side and by noting the exact-Decimal sorting of awards, which clarifies what the results will contain.

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 names a specific verb ('Queries') and two concrete resources with their exact APIs: ClinicalTrials.gov v2 (phase, status, sponsor, conditions, completion dates) and USASpending.gov v2 prime contract awards. This is far more specific than the sibling tools' generic names, and an agent can immediately tell what data comes back.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of alternatives (e.g., fetch_openfda_recalls for recall data), and no stated prerequisites beyond the price tag. The 'mode' selector exists in the schema but the description never explains when to pick 'clinical_trials' vs 'federal_contracts' vs 'both'.

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.