Skip to main content
Glama

get_agency_deficiency_guidance

Retrieve common deficiency areas for FDA or EMA regulatory submissions by selecting agency and domain: CMC, Clinical, Labelling, or Pharmacovigilance.

Instructions

Retrieve common deficiency areas for FDA or EMA submissions by domain (CMC, Clinical, Labelling, Pharmacovigilance).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
agencyYesRegulatory agency: 'FDA' or 'EMA'
domainYesArea: 'CMC', 'Clinical', 'Labelling', or 'Pharmacovigilance'

Implementation Reference

  • src/index.ts:298-309 (registration)
    Tool 'get_agency_deficiency_guidance' is registered in the ListToolsRequestSchema handler with its name, description, and inputSchema (agency + domain as required strings).
    {
              name: "get_agency_deficiency_guidance",
              description: "Retrieve common deficiency areas for FDA or EMA submissions by domain (CMC, Clinical, Labelling, Pharmacovigilance).",
              inputSchema: {
                          type: "object",
                          properties: {
                                        agency: { type: "string", description: "Regulatory agency: 'FDA' or 'EMA'" },
                                        domain: { type: "string", description: "Area: 'CMC', 'Clinical', 'Labelling', or 'Pharmacovigilance'" }
                          },
                          required: ["agency", "domain"]
              }
    },
  • Input schema definition for the tool: requires 'agency' (FDA/EMA) and 'domain' (CMC/Clinical/Labelling/Pharmacovigilance) as string properties.
    inputSchema: {
                type: "object",
                properties: {
                              agency: { type: "string", description: "Regulatory agency: 'FDA' or 'EMA'" },
                              domain: { type: "string", description: "Area: 'CMC', 'Clinical', 'Labelling', or 'Pharmacovigilance'" }
                },
                required: ["agency", "domain"]
    }
  • Handler implementation for the tool. Parses agency/domain args, looks up AGENCY_DEFICIENCIES data map, and returns a formatted list of common deficiencies for that agency and domain, or an error message if not found.
    if (name === "get_agency_deficiency_guidance") {
            const { agency, domain } = z.object({ agency: z.string(), domain: z.string() }).parse(args);
            const agencyData = AGENCY_DEFICIENCIES[agency.toUpperCase()];
            if (!agencyData) return { content: [{ type: "text", text: "Agency " + agency + " not found. Supported: FDA, EMA." }] };
            const deficiencies = agencyData[domain];
            if (!deficiencies) return { content: [{ type: "text", text: "Domain " + domain + " not found for " + agency + ". Available: " + Object.keys(agencyData).join(", ") }] };
            return { content: [{ type: "text", text: "# " + agency.toUpperCase() + " Common Deficiencies — " + domain + "\n\n" + deficiencies.map((d, i) => (i+1) + ". " + d).join("\n") }] };
    }
  • The AGENCY_DEFICIENCIES data constant containing the actual deficiency lists for FDA (CMC, Clinical, Labelling) and EMA (CMC, Clinical, Pharmacovigilance). This is the data source used by the handler.
    const AGENCY_DEFICIENCIES: Record<string, Record<string, string[]>> = {
        FDA: {
              CMC: [
                      "Insufficient process validation data — commercial-scale validation batches required",
                      "Missing or inadequate method validation reports per USP 1225",
                      "Stability data gap — insufficient real-time data to support proposed shelf life",
                      "Impurity qualification threshold not met — genotoxic impurities require ICH M7 assessment",
                      "Container closure integrity testing data absent for parenteral products",
                      "Lack of comparability data for post-approval manufacturing changes"
                    ],
              Clinical: [
                      "Primary endpoint not met with statistical significance in pivotal trial",
                      "Inadequate patient population diversity in clinical studies",
                      "Missing long-term safety data — post-marketing requirement likely",
                      "Drug-drug interaction (DDI) studies incomplete per FDA DDI guidance",
                      "Pediatric study plan (iPSP) not submitted or inadequate",
                      "REMS requirement not addressed — based on safety signals"
                    ],
              Labelling: [
                      "Proposed indication not supported by clinical data",
                      "Dosing recommendations for renal/hepatic impairment absent",
                      "Contraindications section incomplete based on clinical findings",
                      "Pregnancy and lactation data not adequately reflected",
                      "Boxed warning required based on safety profile"
                    ]
        },
        EMA: {
              CMC: [
                      "ASMF/DMF reference incomplete — holder must provide access letter",
                      "Batch analysis data insufficient — minimum 3 pilot/production batches required",
                      "Missing XRPD data for polymorphic forms of API",
                      "Dissolution method not discriminating — robustness data required",
                      "CEP (Certificate of Suitability) required for API from European Pharmacopoeia monograph substance"
                    ],
              Clinical: [
                      "CHMP scientific advice not followed — justification required",
                      "PASS (Post-Authorisation Safety Study) commitments not proposed",
                      "Paediatric Investigation Plan (PIP) compliance not demonstrated",
                      "Benefit-risk balance not clearly articulated in Clinical Overview",
                      "EPAR-relevant information missing from clinical summaries"
                    ],
              Pharmacovigilance: [
                      "Risk Management Plan (RMP) does not address identified risks",
                      "QPPV (Qualified Person for Pharmacovigilance) details incomplete",
                      "Pharmacovigilance system master file (PSMF) location not provided",
                      "Missing routine risk minimisation measures in RMP"
                    ]
        }
    };
Behavior2/5

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

With no annotations, the description carries full burden but only states retrieval; it does not disclose return format, limitations, or authorization requirements, leaving behavioral traits unspecified.

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?

The description is a single, focused sentence that front-loads the core purpose with no extraneous information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description could better specify what 'common deficiency areas' entails (e.g., list of strings) or typical usage patterns, but it is minimally adequate for a straightforward retrieval tool.

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 coverage is 100% and descriptions are clear; the description adds minor value by listing domain options but does not deepen semantic understanding beyond the 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?

The description clearly states the tool retrieves common deficiency areas for FDA or EMA submissions by domain, which is specific and distinct from sibling tools (e.g., check_ctd_completeness, lookup_ich_guideline).

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?

The description provides clear context but no explicit guidance on when to use this tool versus siblings, such as not using it for general ICH guidance or submission checklists.

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

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pubspro/regsub-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server