Skip to main content
Glama

China With Me — Hardware Prototyping & Exhibition MCP

search_china_exhibitions

Read-onlyIdempotent

Search upcoming Chinese trade shows and industrial exhibitions (Canton Fair, CHTF High-Tech Fair, DMP CNC/Mold Industrial Expo, bauma CHINA, Automechanika Shanghai, SEMICON China, electronica China, CIOE Optoelectronics, IOTE IoT, CMEF Medical, etc.) by keyword, category, or city. Expired past shows are automatically excluded.

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": "search_china_exhibitions"
  }
}

Input Schema

NameRequiredDescriptionDefault
cityNoOptional city filter, e.g. 'Shenzhen', 'Shanghai', 'Guangzhou', 'Suzhou', 'Beijing'
queryNoKeyword such as 'CNC', 'sensors', 'robotics', 'semiconductor', 'PCBA', 'medical', 'optics', 'Canton Fair', 'IoT'
categoryNoOptional category filter: 'Manufacturing & CNC', 'Electronics & Hardware', 'Chemicals & Materials', 'Food, Retail & Lifestyle', 'Semiconductors & IC', 'New Energy & Storage', 'Robotics & Automation', 'Medical & Healthcare', 'Optics & Sensors', 'Logistics & E-Commerce', 'Packaging & Printing', 'Automotive & EV'

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional category filter: 'Electronics & Hardware', 'Manufacturing & CNC', 'Optics & Photonics', 'Medical & Healthcare', 'Building & Home'"New value: +"Optional category filter: 'Manufacturing & CNC', 'Electronics & Hardware', 'Chemicals & Materials', 'Food, Retail & Lifestyle', 'Semiconductors & IC', 'New Energy & Storage', 'Robotics & Automation', 'Medical & Healthcare', 'Optics & Sensors', 'Logistics & E-Commerce', 'Packaging & Printing', 'Automotive & EV'"
    • changedInput schema / properties / city / description
      Previous value: -"Optional city filter, e.g. 'Shenzhen', 'Guangzhou', 'Shanghai'"New value: +"Optional city filter, e.g. 'Shenzhen', 'Shanghai', 'Guangzhou', 'Suzhou', 'Beijing'"
    • changedInput schema / properties / query / description
      Previous value: -"Keyword such as 'CNC', 'sensors', 'robotics', 'PCBA', 'medical', 'optics', 'Canton Fair', 'IoT'"New value: +"Keyword such as 'CNC', 'sensors', 'robotics', 'semiconductor', 'PCBA', 'medical', 'optics', 'Canton Fair', 'IoT'"
  2. First observed

TDQS

A3.9/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds one genuinely behavioral fact beyond that: expired past shows are automatically excluded from results. It says nothing about result volume, ranking, pagination, or what fields a match returns, so the added context is real but thin.

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?

Two tight sentences with the search axes and the exclusion rule front-loaded. The parenthetical list of ten trade shows is long, but it earns its place by anchoring the domain and giving the agent recognisable entities; nothing else is wasted.

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 zero-required-parameter read-only search with a fully documented schema and no output schema, the definition covers purpose, scope, and the key filtering behavior. The remaining gap is that it does not describe the shape or size of returned results, which matters less here because safety annotations carry the behavioral burden.

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 all three parameters are already documented with per-parameter examples, so the baseline is 3. The description reinforces that the three axes are keyword, category, and city, but adds no semantics beyond the schema — no note on how parameters combine (AND vs OR), whether one is required, or how free-text query interacts with the category taxonomy.

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?

States a specific verb and resource ('Search upcoming Chinese trade shows and industrial exhibitions') and narrows scope further by naming concrete examples (Canton Fair, bauma CHINA, SEMICON China) plus the three search axes: keyword, category, city. An agent can immediately distinguish this from siblings like request_remote_exhibition_viewer or book_consultation_or_quote, which are actions rather than discovery.

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?

Gives clear usage context: search by keyword, category, or city, and states the exclusion rule that expired past shows are automatically dropped, so the agent knows the result set is forward-looking. It stops short of explicitly naming alternatives or when-not-to-use conditions (e.g., no guidance to use this before requesting a remote viewer), which keeps it below a 5.

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.