DrugBank

Return SDL snippets for named GraphQL types from the bundled MCP endpoint schema (graphql-core print_type). Call before run_query whenever you add or change nested fields: same field names can have different arguments on different parent types (verify per type). Do not infer structure from similar type names— only SDL for each exact type counts (include wrapper types you traverse). Prefer one call with every type you will select under (e.g. ["McpQuery", "Condition", "DecodedConditionDrugs", "DrugConnection"]). After a GraphQL error, load the parent object type of the failing field and fix arguments/subfields from SDL—do not guess. Args: types: Type names to include, e.g. ["Drug", "Condition"]. Omit or pass an empty list to get only the root query type ``McpQuery``. Unknown names are called out in comments; output order matches the request order.

Load DrugBank skill content: primary instructions, named companions, or a topic by resource name. Prefer skill://using-drugbank-mcp/... resources when the client supports them; this tool returns the same text. Call before your first DrugBank GraphQL query for routing and best practices. Args: resource: Defaults to the primary skill. Use "_manifest" for JSON listing all skill files (paths, sizes, and front matter metadata for markdown). Use "mcp-graphql-schema" for the full endpoint SDL file (same source as explore_schema). Other values match the skill package (e.g. api-reference, searching-and-lookups, drug-filters, graphql-entity-types). Hyphens and underscores are equivalent for file-backed resources.

Execute a GraphQL query and return the results. Args: query: The GraphQL query string to execute variables: Optional JSON object containing query variables