Skip to main content
Glama
SignalGrid B2B Intelligence MCP

SignalGrid B2B Intelligence MCP

extract_fda_port_refusal_leads

Read-onlyIdempotent

Extract official FDA OASIS port detention and import refusal records—including manufacturer FEI, address, private-lab gap flags, and violation charges—to identify compliance and lab-testing leads.

Instructions

Extract official US FDA OASIS port detention and import refusal records including foreign manufacturer FEI, full street address, private-lab analysis gap flag, and FD&C Act violation charges (signalgridhq/fda-import-refusal-leads).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "extract_fda_port_refusal_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNo4-digit year of FDA OASIS Import Refusal Reports.
monthNoNumeric month (1-12) of FDA OASIS Import Refusal Reports.
maxItemsNoMaximum dataset items to return in this MCP call (1-200).
countryCodesNo2-letter ISO exporter country codes (e.g. ['VN', 'CN', 'IN', 'MX', 'IT', 'KR', 'TH']).
onlyMissingPrivateLabNoWhen true, filters strictly to detained shipments missing private laboratory sample analysis (highest-intent compliance & lab testing leads).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds that records are 'official' FDA OASIS data and lists the fields exposed, but says nothing about report publication lag, data freshness, volume, or whether calls are rate-limited or metered for an open-world scrape.

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 front-loaded sentence with the resource named first and the returned fields after. The trailing parenthetical '(signalgridhq/fda-import-refusal-leads)' is an internal dataset slug that adds little for an agent choosing a tool, but the rest is dense and waste-free.

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 no output schema, the description does the necessary work of enumerating the returned fields, and all five optional parameters are documented in the schema. The remaining gap is operational: nothing about result ordering, pagination, or how many months of reports are actually available for a requested year/month combination.

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 year/month bounds, countryCodes ISO examples, maxItems range, and an explanation of onlyMissingPrivateLab all documented in the schema. The description contributes no additional parameter meaning such as default behavior, interaction between countryCodes and onlyMissingPrivateLab, or what the default VN/IN/MX filter implies, so the baseline 3 applies.

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 uses a specific verb ('Extract') with a precisely named resource ('US FDA OASIS port detention and import refusal records') and enumerates the payload (foreign manufacturer FEI, street address, private-lab gap flag, FD&C Act charges). It is unambiguous what the tool returns, but it never names or differentiates itself from the sibling extractors, so an agent must infer the distinction from the domain alone.

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?

There is no explicit when-to-use statement, no exclusions, and no reference to the sibling tools (quickbooks/xero lead extractors, preview_sample_b2b_dataset). The lead-generation intent is only implied by the dataset slug and by the parameter note about 'highest-intent compliance & lab testing leads', which lives in the schema rather than the description.

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