DrugBank

Return SDL for GraphQL types on the MCP endpoint, read live from the schema the endpoint serves. A `types` entry can name a whole type or part of one: "Drug" the type "Drug.pharmacology" one field, with its description "Drug.pharmacology.mechanism_of_action" that field, plus one member of the type it returns "FilterInput.indication_*" every argument sharing a prefix "Drug:filters" the filter families an entity accepts "Drug:filters:pharmacology" the filters in one family You get what you asked for, plus what you need to use it: the pagination wrappers, the enums and custom scalars whose values and id formats exist nowhere else, and the type a named coordinate refers to. Other referenced types are named rather than included -- their fields are unknown until you ask, so selecting on one fails. Read the "Referenced but not included" list; each entry names the identity fields that type has, since they differ (Condition has `title` where Drug has `name`). Large containers (FilterInput, Lookups) are summarised, not listed. Responses also carry what SDL cannot: for a filter, which lookup resolves its values, which entities accept it, and which filters take the same values; plus per_page ceilings that clamp silently, and deprecations. Follow the hints in each response. Call before run_query whenever you add or change nested fields: the same field name can take different arguments on different parent types, and similar type names do not imply the same layout. After a GraphQL error, load the parent type of the failing field rather than guessing.

explore_schema

List every DrugBank skill guide that get_drugbank_skill can return, as JSON: each entry's `resource` (the value to pass to get_drugbank_skill), file path, size, and front matter (name and description). Use it to find the guide for a topic before loading it.

list_drugbank_skills

Return one DrugBank skill guide as markdown: the primary guide by default, or a topic guide by resource name. Call it before your first DrugBank GraphQL query for routing and best practices. Use list_drugbank_skills to see every available guide. The same guides are also published as MCP resources under skill://using-drugbank-mcp/.

get_drugbank_skill

Execute a GraphQL query and return the results. A successful response may carry an `extensions.filters` object describing how the query was interpreted -- for example, a filter that matched more records than the values you passed. Each entry has a `summary` sentence. Read it and reflect it when reporting the results, otherwise you may describe a broader answer as a narrower one. If a field is `null` with an `UNSUPPORTED_FILTER` error, nothing ran for it: disregard the parts of `extensions.filters` that concern only that field's filters.

run_query