Skip to main content
Glama

USP Reference Standards catalog search: total matches

health_usp_monographs_standards
Read-only

USP Reference Standards catalog search (official USP Store): total matches and per item the catalog number, name, package size, CAS number, chemical name, molecular formula, category (e.g. Active Pharmaceutical Ingredients), product line, price (USD), in-stock / ready-to-ship flags, current lot number and release date, associated monograph, therapeutic categories and store link. From store.usp.org. 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": {
      "query": "<query>"
    },
    "name": "health_usp_monographs_standards"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoResults to return, 1-50 (default 20)
queryYesSubstance, CAS number or catalog number, e.g. aspirin, 50-78-2, 1044006
offsetNoResults to skip for paging (default 0)

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/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 the description clears a lower bar and still adds real value: cost ($0.002 per successful call), the x402 payment rails (USDC on Base, Solana, etc.), and the fact that failed calls are not charged. It does not mention rate limits or what happens if the calling agent lacks a funded wallet, which is a notable omission for a paid endpoint.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and pricing are front-loaded, which is good, but the middle is a long run-on enumeration of per-item return fields (CAS number, chemical name, molecular formula, category, product line, price, stock flags, lot number, release date, monograph, therapeutic categories, store link) that duplicates the output schema. That list dilutes the sentences that actually matter.

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?

With an output schema present, the description needn't explain return values, and it does supply the two things structured fields don't carry: the data source and the per-call cost/billing model. Complete enough to invoke correctly, with only the payment-setup prerequisite unaddressed.

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%, so query (substance/CAS/catalog number), limit (1-50), and offset are already fully documented. The description adds nothing about parameter behavior, so the 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?

Opens with a specific verb+resource: 'USP Reference Standards catalog search (official USP Store)', and names the source store.usp.org, which no sibling shares. It also states the primary output ('total matches'), so an agent can tell exactly what this returns.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance and no named alternative. The description implies the tool is for looking up reference standards, but an agent is left to infer that from the resource name rather than from any stated routing rule.

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