Skip to main content
Glama
yeyuan98

BioMCP

by yeyuan98
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

drug_search

Read-only

Find drugs by name, synonym, or chemical identifier in ChEMBL/MyChem. Use it for identity lookups; for target or mechanism queries such as "EGFR inhibitor," search by gene symbol instead.

Instructions

Search for drugs by name or keyword (chemical identity: names, synonyms, and identifiers in ChEMBL/MyChem). This is NOT a mechanism or target search — MyChem has no mechanism text in this query, so "EGFR inhibitor"-style queries return nothing. For drugs targeting a gene/mechanism, use gene_drugs with the target gene symbol.

Input Schema

NameRequiredDescriptionDefault
limitNoMaximum results
queryYesDrug name or keyword (chemical identity, e.g. "imatinib"); for target/mechanism queries (e.g. "EGFR inhibitor") use gene_drugs with the gene symbol instead
offsetNoResult offset

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.6.0-alpha.10
    • removedInput schema / additionalProperties
      Removed value: -false
    • addedInput schema / properties / offset / maximum
      Added value: +9007199254740991
  2. Changed1 schema field changedv1.6.0-alpha.2
    • changedInput schema / properties / query / description
      Previous value: -"Drug name, mechanism, or keyword to search"New value: +"Drug name or keyword (chemical identity, e.g. \"imatinib\"); for target/mechanism queries (e.g. \"EGFR inhibitor\") use gene_drugs with the gene symbol instead"
  3. Changed1 schema field changedv1.6.0-alpha.1
    • addedInput schema / properties / query / minLength
      Added value: +1
  4. Changed3 schema fields changedv0.7.1
    • removedInput schema / properties / drug_type
      Removed value: -{
-  "description": "Filter by drug type",
-  "type": "string"
-}
    • changedInput schema / properties / query / description
      Previous value: -"Drug name, mechanism, or keyword to search for"New value: +"Drug name, mechanism, or keyword to search"
    • removedInput schema / properties / source
      Removed value: -{
-  "description": "Filter by source (mychem, chembl, openfda)",
-  "type": "string"
-}
  5. First observedv0.1.8

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds real behavioral context beyond that: mechanism-style queries return nothing because MyChem has no mechanism text, which prevents a common failure. It does not mention pagination behavior or result shape, so it falls short of a 5.

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?

Three tight sentences: positive scope first, the negative constraint second, the alternative third. No filler, and the most important routing information is front-loaded.

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

Completeness5/5

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

For a read-only open-world search with no output schema and fully documented params, the definition covers what an agent needs: correct input type, the failure mode to avoid, and the alternative tool. Nothing essential is missing.

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%, so query, limit, and offset are all documented in the schema itself, and the description's note about chemical identity largely restates the query field. No extra syntax or format guidance beyond what the schema provides, so baseline 3 applies.

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?

States a specific verb and resource (search drugs) plus the scope (chemical identity: names, synonyms, identifiers in ChEMBL/MyChem), and explicitly names the sibling gene_drugs as the different tool. An agent can distinguish it from gene_drugs and drug_get without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when not to use it ('NOT a mechanism or target search') and gives the concrete alternative (gene_drugs with the target gene symbol) with example queries that select each path. This is textbook when/when-not/alternative routing.

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

Deploy Server

Other Tools