Skip to main content
Glama

DEA controlled substance schedules: substance name and DEA

health_dea_controlled_substances
Read-only

DEA controlled substance schedules (21 CFR 1308.11-1308.15, via eCFR): substance name and DEA Controlled Substances Code Number for schedule I to V table entries matching a name. Substances listed only in paragraphs are not searched. Does not include registration status. Up to 20 matches per call. Price: $0.002 per successful call, paid with x402 (USDC on Base, Solana and 10 more networks); failed calls are not charged.

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": {
      "substance": "<substance>"
    },
    "name": "health_dea_controlled_substances"
  }
}

Input Schema

NameRequiredDescriptionDefault
maxNoHow many matches, 1 to 20 (default 10)
substanceYesSubstance name words, letters, spaces and hyphens, 3 to 60 characters

Output Schema

NameRequiredDescriptionDefault
asOfNo
queryNo
totalNo
sourceNo
matchesNo
checkedAtNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Beyond the read-only and open-world annotations, the description discloses the pricing model ($0.002 per successful call via x402, failed calls not charged), the 20-match cap, and important coverage exclusions. These are practical behavioral details that materially affect invocation and budgeting.

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?

The description is front-loaded with the resource and scope, then efficiently adds exclusions, limits, and cost. It is dense but not wasteful; the payment-network enumeration is somewhat long but still relevant to the pricing behavior.

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?

Given the output schema and annotations, the description supplies the remaining context an agent needs: search scope, exclusions, maximum matches, and payment terms. No material invocation detail appears to be 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 description coverage is 100%, and the schema already documents the substance format and max range/default. The description adds only that matching is by name and reinforces the 20-match limit, so it does not add much parameter meaning 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 states a specific lookup over DEA controlled substance schedules, returning substance name and DEA code for schedule I–V table entries matching a name. It also distinguishes the scope by excluding paragraph-only listings and registration status, so an agent can tell what this tool does and does not cover.

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?

It gives clear contextual exclusions: paragraph-only listed substances are not searched and registration status is not included. It does not explicitly name an alternative tool for registration lookups, but the when-to-use boundary is clear for name-based schedule matching.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources