Skip to main content
Glama

Get Bioactivity

pubchem_get_bioactivity
Read-onlyIdempotent

Retrieve a compound's bioactivity profile, including assays, outcomes, targets, quantitative values, and PubMed IDs. Filter by activity outcome, molecular target, or assay type to focus results.

Instructions

Get a compound's bioactivity profile: which assays tested it, activity outcomes (Active/Inactive/Inconclusive), target identifiers (NCBI Gene ID, UniProt/GenBank accession), quantitative values (IC50, EC50, Ki, etc.), each assay's type (confirmatory, screening, summary, other), and the PubMed IDs it cites. Filter by outcome, a specific molecular target (NCBI Gene ID or protein accession), and/or assay type to focus the profile — e.g. "is this compound active against target T in confirmatory assays?".

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "cid": "<cid>"
    },
    "name": "pubchem_get_bioactivity"
  }
}

Input Schema

NameRequiredDescriptionDefault
cidYesPubChem Compound ID. Resolve from name/SMILES with pubchem_search_compounds.
offsetNoZero-based index of the first assay to return, applied after the outcome and target filters. Pass the nextOffset from a previous call to read the following page. Default: 0.
assayTypeNoKeep only assays of these types: "confirmatory" (dose-response and other follow-up assays), "screening" (primary high-throughput screens), "summary" (records summarizing a project's assays), "other". Matched against PubChem's Assay Type regardless of case; an assay with no recorded type matches none. Combines with outcomeFilter and the target filters — an assay must pass all of them. Omit to keep every type.
maxResultsNoMax assay results to return per page. The per-call cap is 100: a larger value (up to 1000) returns a page of 100 and is reported in cappedInputs. Well-studied compounds have thousands of records; use offset to reach the ones past this page. Default: 20.
targetGeneIdNoFilter to assays against this NCBI Gene ID (1 to 2147483647), including assays recorded only under a protein accession this compound's assay table pairs with the Gene ID (e.g. 5742 also reaches rows carrying only P23219 when another row pairs the two). Obtain Gene IDs from the GeneID:N in a pubchem_get_compound_interactions target entry's partner (kinds: ["target"]) or the targetGeneId field of a result here without a target filter (rows from untargeted screens carry none). Combine with outcomeFilter="active" to answer "is this compound active against target T?".
outcomeFilterNoFilter by activity outcome against each assay's reported target: the target a target filter matched, else the first target the assay lists. For a multi-target assay, outcomes against its other targets (in otherTargets) do not count. "active" keeps assays where that outcome is Active — most useful for understanding biological profile. Default: "all".all
targetAccessionNoFilter to assays against this target protein accession (UniProt/RefSeq/GenBank/PDB chain), e.g. "P35354", including assays recorded only under a Gene ID or another accession this compound's assay table pairs with it. Uppercased before matching; a PDB chain ID (the "A" in "1ZHH_A") is kept as given. With targetGeneId, both must name the same target — when the table ties them to different targets, nothing matches. Obtain accessions from an assay's targets in pubchem_get_summary (entityType "assay"), the accession:X in a pubchem_get_compound_interactions target entry's partner, or the targetAccession field of a result here without a target filter.

Output Schema

NameRequiredDescriptionDefault
capNoThe page size applied: maxResults, or the per-call cap when maxResults exceeds it.
cidNoPubChem Compound ID.
errorNoPresent when the call failed. Absent on success.
shownNoAssays returned on this page.
noticeNoRecovery guidance when the filter yields no results or the compound has no bioactivity data.
offsetNoZero-based index of the first assay returned.
resultsNoAssay results matching the filter.
truncatedNoTrue when matching assays remain past this page.
nextOffsetNoOffset to pass on the next call to continue past this page. Omitted when no further assays match.
activeCountNoAssays whose outcome against their first listed target is "Active", across all assays and before any filter. A multi-target assay counts by its first target only.
totalAssaysNoTotal unique assays for this compound.
cappedInputsNoInputs that asked for more than their per-call cap, with the value requested and the value served. An ID batch lists the IDs past the cap in unprocessed. Omitted when every input was within its cap.
targetFilterNoTarget identifiers matched, when a target filter is set: those passed plus every Gene ID and accession the compound's assay table pairs with them. When the two inputs name different targets, only the two inputs.
filteredCountNoExact number of assays matching the outcome, target, and assay-type filters, across all pages.
inactiveCountNoAssays whose outcome against their first listed target is "Inactive", across all assays and before any filter. A multi-target assay counts by its first target only.
outcomeFilterNoOutcome filter applied: active, inactive, or all.
returnedCountNoAssays returned on this page.
assayTypeFilterNoAssay types kept, comma-separated (e.g. "confirmatory, summary"), when assayType is set.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.8.0
    • changedInput schema / properties / targetAccession / description
      Previous value: -"Filter to assays against this target protein accession (UniProt/RefSeq/GenBank/PDB chain), e.g. \"P35354\", including assays recorded only under a Gene ID or another accession this compound's assay table pairs with it. Uppercased before matching; a PDB chain ID (the \"A\" in \"1ZHH_A\") is kept as given. With targetGeneId, both must name the same target — when the table ties them to different targets, nothing matches. Obtain accessions from pubchem_search_assays or the targetAccession field of an unfiltered result here."New value: +"Filter to assays against this target protein accession (UniProt/RefSeq/GenBank/PDB chain), e.g. \"P35354\", including assays recorded only under a Gene ID or another accession this compound's assay table pairs with it. Uppercased before matching; a PDB chain ID (the \"A\" in \"1ZHH_A\") is kept as given. With targetGeneId, both must name the same target — when the table ties them to different targets, nothing matches. Obtain accessions from an assay's targets in pubchem_get_summary (entityType \"assay\"), the accession:X in a pubchem_get_compound_interactions target entry's partner, or the targetAccession field of a result here without a target filter."
    • changedInput schema / properties / targetGeneId / description
      Previous value: -"Filter to assays against this NCBI Gene ID (1 to 2147483647), including assays recorded only under a protein accession this compound's assay table pairs with the Gene ID (e.g. 5742 also reaches rows carrying only P23219 when another row pairs the two). Obtain Gene IDs from pubchem_search_assays or the targetGeneId field of an unfiltered result here. Combine with outcomeFilter=\"active\" to answer \"is this compound active against target T?\"."New value: +"Filter to assays against this NCBI Gene ID (1 to 2147483647), including assays recorded only under a protein accession this compound's assay table pairs with the Gene ID (e.g. 5742 also reaches rows carrying only P23219 when another row pairs the two). Obtain Gene IDs from the GeneID:N in a pubchem_get_compound_interactions target entry's partner (kinds: [\"target\"]) or the targetGeneId field of a result here without a target filter (rows from untargeted screens carry none). Combine with outcomeFilter=\"active\" to answer \"is this compound active against target T?\"."
  2. Changed5 schema fields changedv0.7.1
    • addedInput schema / properties / assayType
      Added value: +{
      +  "description": "Keep only assays of these types: \"confirmatory\" (dose-response and other follow-up assays), \"screening\" (primary high-throughput screens), \"summary\" (records summarizing a project's assays), \"other\". Matched against PubChem's Assay Type regardless of case; an assay with no recorded type matches none. Combines with outcomeFilter and the target filters — an assay must pass all of them. Omit to keep every type.",
      +  "items": {
      +    "enum": [
      +      "confirmatory",
      +      "screening",
      +      "summary",
      +      "other"
      +    ],
      +    "type": "string"
      +  },
      +  "minItems": 1,
      +  "type": "array"
      +}
    • addedOutput schema / properties / assayTypeFilter
      Added value: +{
      +  "description": "Assay types kept, comma-separated (e.g. \"confirmatory, summary\"), when assayType is set.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / filteredCount / description
      Previous value: -"Exact number of assays matching the outcome and target filters, across all pages."New value: +"Exact number of assays matching the outcome, target, and assay-type filters, across all pages."
    • addedOutput schema / properties / results / items / properties / assayType
      Added value: +{
      +  "description": "PubChem's assay type as written: Confirmatory, Screening, Summary, or Other. Omitted when PubChem records none.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / results / items / properties / pmids
      Added value: +{
      +  "description": "PubMed IDs of the publications the assay cites, highest (most recently assigned) first. Omitted when it cites none.",
      +  "items": {
      +    "type": "number"
      +  },
      +  "type": "array"
      +}
  3. Changed17 schema fields changedv0.7.0
    • changedInput schema / properties / cid / maximum
      Previous value: -9007199254740991New value: +2147483647
    • changedInput schema / properties / maxResults / description
      Previous value: -"Max assay results to return per page (1-100). Well-studied compounds have thousands of records; use offset to reach the ones past this page. Default: 20."New value: +"Max assay results to return per page. The per-call cap is 100: a larger value (up to 1000) returns a page of 100 and is reported in cappedInputs. Well-studied compounds have thousands of records; use offset to reach the ones past this page. Default: 20."
    • changedInput schema / properties / maxResults / maximum
      Previous value: -100New value: +1000
    • changedInput schema / properties / outcomeFilter / description
      Previous value: -"Filter by activity outcome. \"active\" shows only assays where the compound showed activity — most useful for understanding biological profile. Default: \"all\"."New value: +"Filter by activity outcome against each assay's reported target: the target a target filter matched, else the first target the assay lists. For a multi-target assay, outcomes against its other targets (in otherTargets) do not count. \"active\" keeps assays where that outcome is Active — most useful for understanding biological profile. Default: \"all\"."
    • changedInput schema / properties / targetAccession / description
      Previous value: -"Filter to assays against this target protein accession (UniProt/GenBank), e.g. \"P35354\". Obtain accessions from pubchem_search_assays or the targetAccession field of an unfiltered result here."New value: +"Filter to assays against this target protein accession (UniProt/RefSeq/GenBank/PDB chain), e.g. \"P35354\", including assays recorded only under a Gene ID or another accession this compound's assay table pairs with it. Uppercased before matching; a PDB chain ID (the \"A\" in \"1ZHH_A\") is kept as given. With targetGeneId, both must name the same target — when the table ties them to different targets, nothing matches. Obtain accessions from pubchem_search_assays or the targetAccession field of an unfiltered result here."
    • changedInput schema / properties / targetGeneId / description
      Previous value: -"Filter to assays against this NCBI Gene ID. Obtain Gene IDs from pubchem_search_assays or the targetGeneId field of an unfiltered result here. Combine with outcomeFilter=\"active\" to answer \"is this compound active against target T?\"."New value: +"Filter to assays against this NCBI Gene ID (1 to 2147483647), including assays recorded only under a protein accession this compound's assay table pairs with the Gene ID (e.g. 5742 also reaches rows carrying only P23219 when another row pairs the two). Obtain Gene IDs from pubchem_search_assays or the targetGeneId field of an unfiltered result here. Combine with outcomeFilter=\"active\" to answer \"is this compound active against target T?\"."
    • changedInput schema / properties / targetGeneId / maximum
      Previous value: -9007199254740991New value: +2147483647
    • changedOutput schema / properties / activeCount / description
      Previous value: -"Assays with \"Active\" outcome."New value: +"Assays whose outcome against their first listed target is \"Active\", across all assays and before any filter. A multi-target assay counts by its first target only."
    • changedOutput schema / properties / cap / description
      Previous value: -"The maxResults cap that was applied."New value: +"The page size applied: maxResults, or the per-call cap when maxResults exceeds it."
    • addedOutput schema / properties / cappedInputs
      Added value: +{
      +  "description": "Inputs that asked for more than their per-call cap, with the value requested and the value served. An ID batch lists the IDs past the cap in unprocessed. Omitted when every input was within its cap.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "One input served at its per-call cap.",
      +    "properties": {
      +      "input": {
      +        "description": "Input name, e.g. \"maxResults\" or \"cids\".",
      +        "type": "string"
      +      },
      +      "requested": {
      +        "description": "Value requested: the page size, or the number of IDs in the batch.",
      +        "type": "number"
      +      },
      +      "served": {
      +        "description": "Value served: the per-call cap.",
      +        "type": "number"
      +      },
      +      "unprocessed": {
      +        "description": "ID batches only: IDs past the cap, listed in unprocessed in input order.",
      +        "type": "number"
      +      }
      +    },
      +    "required": [
      +      "input",
      +      "requested",
      +      "served"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / inactiveCount / description
      Previous value: -"Assays with \"Inactive\" outcome."New value: +"Assays whose outcome against their first listed target is \"Inactive\", across all assays and before any filter. A multi-target assay counts by its first target only."
    • changedOutput schema / properties / results / items / properties / activityValues / description
      Previous value: -"Quantitative activity measurements."New value: +"Quantitative activity measurements against the reported target."
    • addedOutput schema / properties / results / items / properties / otherTargets
      Added value: +{
      +  "description": "The assay's other targets, each with its own outcome and measurements. Present only for an assay whose rows name more than one target.",
      +  "items": {
      +    "additionalProperties": false,
      +    "description": "Another target of the assay, with its own outcome and values.",
      +    "properties": {
      +      "accession": {
      +        "description": "Protein accession. Omitted when the row names none.",
      +        "type": "string"
      +      },
      +      "activityValues": {
      +        "description": "Quantitative activity measurements against this target.",
      +        "items": {
      +          "additionalProperties": false,
      +          "description": "Quantitative activity measurement entry.",
      +          "properties": {
      +            "name": {
      +              "description": "Measurement name (e.g. IC50, EC50, Ki). Omitted when not reported.",
      +              "type": "string"
      +            },
      +            "unit": {
      +              "description": "Unit of measurement (e.g. uM, nM). Omitted when not reported.",
      +              "type": "string"
      +            },
      +            "value": {
      +              "description": "Measured value.",
      +              "type": "number"
      +            }
      +          },
      +          "required": [
      +            "value"
      +          ],
      +          "type": "object"
      +        },
      +        "type": "array"
      +      },
      +      "geneId": {
      +        "description": "NCBI Gene ID. Omitted when the row names none.",
      +        "type": "number"
      +      },
      +      "outcome": {
      +        "description": "Activity outcome against this target.",
      +        "type": "string"
      +      }
      +    },
      +    "required": [
      +      "outcome",
      +      "activityValues"
      +    ],
      +    "type": "object"
      +  },
      +  "type": "array"
      +}
    • changedOutput schema / properties / results / items / properties / outcome / description
      Previous value: -"Activity outcome: Active, Inactive, Inconclusive, Unspecified."New value: +"Activity outcome against the reported target — the one a target filter matched, else the assay's first: Active, Inactive, Inconclusive, Unspecified."
    • changedOutput schema / properties / results / items / properties / targetAccession / description
      Previous value: -"Target protein accession (UniProt/GenBank)."New value: +"Reported target's protein accession (UniProt/RefSeq/GenBank/PDB chain)."
    • changedOutput schema / properties / results / items / properties / targetGeneId / description
      Previous value: -"Target NCBI Gene ID."New value: +"Reported target's NCBI Gene ID."
    • changedOutput schema / properties / targetFilter / description
      Previous value: -"Target filter applied (gene ID and/or protein accession), when set."New value: +"Target identifiers matched, when a target filter is set: those passed plus every Gene ID and accession the compound's assay table pairs with them. When the two inputs name different targets, only the two inputs."
  4. Changed4 schema fields changedv0.6.5
    • removedInput schema / properties / cid / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / cid / minimum
      Added value: +1
    • removedInput schema / properties / targetGeneId / exclusiveMinimum
      Removed value: -0
    • addedInput schema / properties / targetGeneId / minimum
      Added value: +1
  5. Changed6 schema fields changedv0.6.1
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedInput schema / additionalProperties
      Added value: +false
    • changedOutput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • addedOutput schema / anyOf
      Added value: +[
      +  {
      +    "not": {
      +      "required": [
      +        "error"
      +      ]
      +    },
      +    "required": [
      +      "cid",
      +      "totalAssays",
      +      "activeCount",
      +      "inactiveCount",
      +      "results",
      +      "outcomeFilter",
      +      "filteredCount",
      +      "returnedCount",
      +      "offset"
      +    ]
      +  },
      +  {
      +    "required": [
      +      "error"
      +    ]
      +  }
      +]
    • addedOutput schema / properties / error
      Added value: +{
      +  "additionalProperties": {},
      +  "description": "Present when the call failed. Absent on success.",
      +  "properties": {
      +    "code": {
      +      "description": "JSON-RPC error code for this failure.",
      +      "maximum": 9007199254740991,
      +      "minimum": -9007199254740991,
      +      "type": "integer"
      +    },
      +    "data": {
      +      "additionalProperties": {},
      +      "properties": {
      +        "reason": {
      +          "description": "Machine-readable failure mode.",
      +          "type": "string"
      +        },
      +        "recovery": {
      +          "additionalProperties": {},
      +          "description": "Actionable next step for the caller.",
      +          "properties": {
      +            "hint": {
      +              "type": "string"
      +            }
      +          },
      +          "required": [
      +            "hint"
      +          ],
      +          "type": "object"
      +        },
      +        "retryable": {
      +          "description": "Whether retrying may succeed.",
      +          "type": "boolean"
      +        }
      +      },
      +      "type": "object"
      +    },
      +    "message": {
      +      "description": "Human-readable description of what went wrong.",
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "code",
      +    "message"
      +  ],
      +  "type": "object"
      +}
    • removedOutput schema / required
      Removed value: -[
      -  "cid",
      -  "totalAssays",
      -  "activeCount",
      -  "inactiveCount",
      -  "results",
      -  "outcomeFilter",
      -  "filteredCount",
      -  "returnedCount",
      -  "offset"
      -]
  6. Changed10 schema fields changedv0.6.0
    • changedInput schema / properties / maxResults / description
      Previous value: -"Max assay results to return (1-100). Well-studied compounds have thousands of records. Default: 20."New value: +"Max assay results to return per page (1-100). Well-studied compounds have thousands of records; use offset to reach the ones past this page. Default: 20."
    • changedInput schema / properties / maxResults / type
      Previous value: -"number"New value: +"integer"
    • addedInput schema / properties / offset
      Added value: +{
      +  "default": 0,
      +  "description": "Zero-based index of the first assay to return, applied after the outcome and target filters. Pass the nextOffset from a previous call to read the following page. Default: 0.",
      +  "maximum": 9007199254740991,
      +  "minimum": 0,
      +  "type": "integer"
      +}
    • changedOutput schema / properties / filteredCount / description
      Previous value: -"Assays matching the outcome and target filters, before the maxResults cap."New value: +"Exact number of assays matching the outcome and target filters, across all pages."
    • addedOutput schema / properties / nextOffset
      Added value: +{
      +  "description": "Offset to pass on the next call to continue past this page. Omitted when no further assays match.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / offset
      Added value: +{
      +  "description": "Zero-based index of the first assay returned.",
      +  "type": "number"
      +}
    • changedOutput schema / properties / returnedCount / description
      Previous value: -"Assays returned after the maxResults cap."New value: +"Assays returned on this page."
    • changedOutput schema / properties / shown / description
      Previous value: -"Assays returned after the maxResults cap."New value: +"Assays returned on this page."
    • changedOutput schema / properties / truncated / description
      Previous value: -"True when results were capped at maxResults — more matching assays exist."New value: +"True when matching assays remain past this page."
    • changedOutput schema / required
      Previous value: -[
      -  "cid",
      -  "totalAssays",
      -  "activeCount",
      -  "inactiveCount",
      -  "results",
      -  "outcomeFilter",
      -  "filteredCount",
      -  "returnedCount"
      -]New value: +[
      +  "cid",
      +  "totalAssays",
      +  "activeCount",
      +  "inactiveCount",
      +  "results",
      +  "outcomeFilter",
      +  "filteredCount",
      +  "returnedCount",
      +  "offset"
      +]
  7. Changed3 schema fields changedv0.2.4
    • addedOutput schema / properties / cap
      Added value: +{
      +  "description": "The maxResults cap that was applied.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / shown
      Added value: +{
      +  "description": "Assays returned after the maxResults cap.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / truncated
      Added value: +{
      +  "description": "True when results were capped at maxResults — more matching assays exist.",
      +  "type": "boolean"
      +}
  8. Changed8 schema fields changedv0.2.2
    • addedInput schema / properties / targetAccession
      Added value: +{
      +  "description": "Filter to assays against this target protein accession (UniProt/GenBank), e.g. \"P35354\". Obtain accessions from pubchem_search_assays or the targetAccession field of an unfiltered result here.",
      +  "type": "string"
      +}
    • addedInput schema / properties / targetGeneId
      Added value: +{
      +  "description": "Filter to assays against this NCBI Gene ID. Obtain Gene IDs from pubchem_search_assays or the targetGeneId field of an unfiltered result here. Combine with outcomeFilter=\"active\" to answer \"is this compound active against target T?\".",
      +  "exclusiveMinimum": 0,
      +  "maximum": 9007199254740991,
      +  "type": "integer"
      +}
    • addedOutput schema / properties / filteredCount
      Added value: +{
      +  "description": "Assays matching the outcome and target filters, before the maxResults cap.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / notice
      Added value: +{
      +  "description": "Recovery guidance when the filter yields no results or the compound has no bioactivity data.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / outcomeFilter
      Added value: +{
      +  "description": "Outcome filter applied: active, inactive, or all.",
      +  "type": "string"
      +}
    • addedOutput schema / properties / returnedCount
      Added value: +{
      +  "description": "Assays returned after the maxResults cap.",
      +  "type": "number"
      +}
    • addedOutput schema / properties / targetFilter
      Added value: +{
      +  "description": "Target filter applied (gene ID and/or protein accession), when set.",
      +  "type": "string"
      +}
    • changedOutput schema / required
      Previous value: -[
      -  "cid",
      -  "totalAssays",
      -  "activeCount",
      -  "inactiveCount",
      -  "results"
      -]New value: +[
      +  "cid",
      +  "totalAssays",
      +  "activeCount",
      +  "inactiveCount",
      +  "results",
      +  "outcomeFilter",
      +  "filteredCount",
      +  "returnedCount"
      +]
  9. Changed6 schema fields changedv0.1.22
    • changedInput schema / properties / cid / description
      Previous value: -"PubChem Compound ID."New value: +"PubChem Compound ID. Resolve from name/SMILES with pubchem_search_compounds."
    • addedOutput schema / properties / results / items / description
      Added value: +"Assay result entry."
    • addedOutput schema / properties / results / items / properties / activityValues / items / description
      Added value: +"Quantitative activity measurement entry."
    • changedOutput schema / properties / results / items / properties / activityValues / items / properties / name / description
      Previous value: -"Measurement name (e.g. IC50, EC50, Ki)."New value: +"Measurement name (e.g. IC50, EC50, Ki). Omitted when not reported."
    • changedOutput schema / properties / results / items / properties / activityValues / items / properties / unit / description
      Previous value: -"Unit of measurement (e.g. uM, nM)."New value: +"Unit of measurement (e.g. uM, nM). Omitted when not reported."
    • changedOutput schema / properties / results / items / properties / activityValues / items / required
      Previous value: -[
      -  "name",
      -  "value",
      -  "unit"
      -]New value: +[
      +  "value"
      +]
  10. First observedv0.1.11

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent and openWorld, so the safety profile is covered. The description adds the notion that the result is a filterable 'profile' but omits operational behavior the caller cares about — pagination, the per-call cap and how capped requests are reported — all of which live only in the schema text. Non-contradictory but not richly additive.

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?

Front-loaded with the resource and its return shape, then a second sentence on filtering with a concrete example question. Dense but every clause maps to a real capability; no filler.

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?

Given an output schema exists, the description needn't explain returns, and it does adequately signal what kind of record set is produced plus how to narrow it. The main residual gap is pagination/capping behavior for well-studied compounds, which an agent must discover from the parameter descriptions.

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 the schema already explains cid, offset, assayType, maxResults, targetGeneId, targetAccession and outcomeFilter in depth. The description only restates the filter axes in prose ('filter by outcome, a specific molecular target, and/or assay type') and adds no syntax, precedence or edge-case detail beyond what the schema provides. Baseline 3 is appropriate.

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 ('Get a compound's bioactivity profile') and then enumerates the returned content: assays, activity outcomes, target identifiers, quantitative values (IC50/EC50/Ki), assay types and PubMed IDs. Among siblings like get_compound_details, get_compound_interactions and search_assays, this clearly occupies the 'bioactivity records for one compound' slot without overlap.

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

Usage Guidelines4/5

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

Offers a concrete usage framing ('is this compound active against target T in confirmatory assays?') and names the three filter axes that narrow the profile. It does not, however, explicitly exclude scenarios or route to a sibling (e.g. when to prefer pubchem_get_compound_interactions or pubchem_search_assays instead).

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