Skip to main content
Glama

Tcm Product Manufacturers

tcm_product_manufacturers
Read-onlyIdempotent

Manufacturers of Singapore HSA-licensed Traditional Chinese Medicine (TCM) / Chinese Proprietary Medicine products, aggregated from data.gov.sg with licensed-product counts and countries, the supply-chain view (who makes licensed CPM products, where). Optionally filter by country of manufacture or manufacturer name. 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": {
      "country": "SINGAPORE"
    },
    "name": "tcm_product_manufacturers"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoMax manufacturers returned, 1-500 (default 50), sorted by licensed-product count
countryNoCountry of manufacture contains (case-insensitive), e.g. "CHINA"
manufacturerNoManufacturer name contains (case-insensitive)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare read-only, idempotent, open-world, non-destructive behavior, so the bar is lower; the description still earns credit by disclosing what the data means and does not mean, i.e. that an HSA licence is a safety-and-quality listing and not efficacy evidence, and that the dataset carries no ingredients or indications. That guards against a common misinterpretation. It does not cover pagination or aggregation freshness, which keeps it 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.

Conciseness4/5

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

The resource and scope are front-loaded in the first sentence before the filters and caveats, and the sentences are purposeful. There is mild redundancy between 'The dataset carries no ingredients and no indications' and the preceding efficacy caveat, and the phrasing 'the supply-chain view (who makes licensed CPM products, where)' repeats the opening clause.

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?

For a three-optional-parameter read tool with no output schema, the definition covers source, scope, return content ('licensed-product counts and countries'), filter behavior, and the key interpretive limit on licence data. What is missing is minor: nothing is said about result ordering guarantees beyond the schema's sort note or about empty-result behavior.

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 the schema already documents limit (1-500, default 50, sorted by count), country (case-insensitive contains), and manufacturer (case-insensitive contains). The description only restates that country and manufacturer filters are optional and adds no syntax, matching behavior, or combination guidance beyond the schema, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific resource and scope: manufacturers of Singapore HSA-licensed TCM/CPM products, sourced from data.gov.sg, with licensed-product counts and countries, framed as 'the supply-chain view (who makes licensed CPM products, where)'. That framing separates it conceptually from the product-level sibling tcm_product_search, though it never names that sibling or states the pivot explicitly.

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

Usage Guidelines3/5

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

Useful context is given for the filters ('optionally filter by country of manufacture or manufacturer name'), and the supply-chain framing implies when the tool is appropriate. However, there is no explicit when-to-use/when-not statement and no named alternative for agents that actually want ingredients, indications, or product-level detail.

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.