Skip to main content
Glama
Sign In
x402-mcp

x402-mcp

Official
by x402node
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

cn402_tcm_meridian

Look up 12 main TCM meridians with element, organ system, flow time, and key acupoints. Supports optional meridian name filter.

Instructions

TCM meridian / Chinese medicine acupuncture meridian / 经络 / 12 meridians / Lung Heart Pericardium Spleen Liver Kidney / 肺经心经 / acupoints / meridian flow time / acupuncture channels / Chinese energy channels. Look up the 12 main TCM meridians with element, organ system, flow time, and key acupoints.

Price: unknown on Base (auto-paid in USDC).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "cn402_tcm_meridian"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoMeridian name (optional: 肺/Lung, 心/Heart, etc; default returns all)

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.1/5.0
Behavior3/5

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

No annotations are provided, so the description must disclose behavior. It indicates that the tool returns specific meridian data and mentions a price (suggesting cost), but does not clarify if the operation is read-only, any rate limits, or effects. The price note adds some transparency but is vague.

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 somewhat keyword-heavy with Chinese characters and lists, but the key sentence 'Look up the 12 main TCM meridians...' is clear and front-loaded. The price line is separate. Could be more streamlined, but not overly verbose.

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 the tool's simplicity (one optional param, no output schema), the description covers the main outputs and usage. It lacks details on exact name formats or error cases, but is sufficient for a basic lookup tool. The price mention adds contextual completeness about cost.

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 coverage is 100% (one parameter 'name' with description). The description adds value by explaining the default behavior (returns all meridians if name omitted) and detailing what fields are returned (element, organ system, flow time, key acupoints), which goes 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 clearly states the tool is for looking up TCM meridians with specific attributes (element, organ system, flow time, key acupoints). It uses multiple related terms and explicitly distinguishes its domain from sibling tools like tcm_herb or tcm_constitution.

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 implies usage for meridian-related queries and mentions the optional name parameter, but does not explicitly compare with siblings or state when not to use it. The context is clear enough for most agents, but lacks explicit guidance on alternatives.

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

Deploy Server

Other Tools