Skip to main content
Glama
Sign In

Tcm Products

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Tcm Product Search

tcm_product_search
Read-onlyIdempotent

Search ~12,000 Traditional Chinese Medicine (TCM) / Chinese Proprietary Medicine products licensed by Singapore's Health Sciences Authority (HSA), sourced from data.gov.sg. Matches Chinese characters (板蓝根), pinyin with or without spaces (banlangen / Ban Lan Gen), and English brand or product names — the licensed name fields carry both scripts. Filter by company, manufacturer, country of manufacture, or dosage form. An HSA licence is a safety-and-quality listing ONLY — it is NOT evidence the product treats any condition. The dataset carries no ingredients and no indications; it is a product inventory.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "板蓝根"
    },
    "name": "tcm_product_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax products returned, 1-200 (default 25)
queryNoProduct or brand name in Chinese characters, pinyin (spaced or not), or English — e.g. "板蓝根", "banlangen", "Ban Lan Gen", "SANJIN". Omit to list by filters alone.
offsetNo0-based offset into the matches, for paging
companyNoLicence-holding company name contains (case-insensitive), e.g. "EU YAN SANG"
countryNoCountry of manufacture contains (case-insensitive), e.g. "CHINA", "SINGAPORE"
dosage_formNoDosage form contains (case-insensitive), e.g. "granules", "capsules", "pills"
manufacturerNoManufacturer name contains (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior5/5

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive. The description adds substantial behavioral context beyond those flags: the exact dataset scale and source, cross-script matching behavior, absence of ingredients and indications, and the regulatory caveat about HSA licences. This meaningfully helps an agent understand what the tool will and will not tell it.

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?

The description is dense but well-organized: dataset identity and source, matching behavior, filter options, then a critical caveat. Every sentence carries information an agent needs, and the most identifying details are front-loaded. No filler or redundancy.

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 search tool with seven optional parameters, no output schema, and rich annotations, the description covers all necessary decision points: what is searched, how text is matched, what filters exist, dataset limitations, and the non-therapeutic meaning of an HSA licence. Pagination details are already in the schema, so the description doesn't need to repeat them.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so each parameter is already documented. The description adds value by summarizing the query semantics ('Matches Chinese characters, pinyin with or without spaces, and English brand or product names') and the filter dimensions, and by explaining why those match modes work ('the licensed name fields carry both scripts'). This goes beyond a bare baseline without needing to repeat per-parameter details.

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 opens with a specific verb and resource: 'Search ~12,000 Traditional Chinese Medicine (TCM) / Chinese Proprietary Medicine products licensed by Singapore's Health Sciences Authority (HSA)'. It also explains the matching modes (Chinese characters, pinyin, English) and available filters, making the tool's scope unmistakable. While it does not explicitly name sibling tcm_product_manufacturers, its focus on product inventory rather than manufacturer lists clearly differentiates it.

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?

The description gives clear context for when to use the tool: searching a product inventory, with filters by company, manufacturer, country, or dosage form. It also provides an important exclusion—this is only a product inventory, not a source for ingredients or indications, and an HSA licence is not efficacy evidence. It does not explicitly say when to prefer a sibling tool, but the context is strong enough.

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

All Tcm Products toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources