Skip to main content
Glama
hkopenai

Hong Kong Creative Goods Trade MCP Server

by hkopenai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Hong Kong Creative Goods Trade MCP Server

GitHub Repository License: MIT

This is an MCP server that provides access to Recreation, Sports and Culture data in Hong Kong through a FastMCP interface.

Features

Creative Goods Trade

  • Get Domestic Exports, Re-exports and Imports of Creative Goods in Hong Kong

  • Filter by year range (optional)

Related MCP server: Hong Kong Food Data MCP Server

Data Source

  • Creative goods trade data from Culture, Sports and Tourism Bureau

Examples

  • Get creative goods trade statistics of Hong Kong

Setup

  1. Clone this repository

  2. Install Python dependencies:

    pip install -r requirements.txt

  3. Run the server:

    python server.py

Running Options

  • Default stdio mode: python server.py

  • SSE mode (port 8000): python server.py --sse

Cline Integration

To connect this MCP server to Cline using stdio:

  1. Add this configuration to your Cline MCP settings (cline_mcp_settings.json):

{
  "hk-recreation": {
    "disabled": false,
    "timeout": 3,
    "type": "stdio",
    "command": "uvx",
    "args": [
      "hkopenai.hk-recreation-mcp-server"
    ]
  }
}

Testing

Tests are available in the tests/ directory. Run with:

pytest

Available Tools

1 tool
get_creative_goods_tradeC

Domestic Exports, Re-exports and Imports of Creative Goods in Hong Kong

ParametersJSON Schema
NameRequiredDescriptionDefault
end_yearNoEnd year of range
start_yearNoStart year of range

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

C2.6/5.0
Behavior1/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says nothing about what the tool returns, default handling of null year parameters, possible aggregation, or any restrictions. The only implied behavior is 'get' from the tool name, which is insufficient.

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 description is short and contains no fluff, but it is structured as a title rather than a functional sentence. It is under-specified for an action-oriented tool description; conciseness is fine but at the cost of clarity and completeness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given that the tool has optional year parameters, no annotations, and no explanation of default behavior, the description leaves too much to inference. Even though an output schema exists and parameters are documented in the schema, the sparse topic-only description does not give an agent enough context to select and invoke the tool confidently.

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%, with both parameters documented as start and end year of range. The description adds no parameter-level meaning beyond the schema, which is the baseline expectation when the schema already covers the parameters.

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?

The description clearly identifies the data resource: Domestic Exports, Re-exports and Imports of Creative Goods in Hong Kong. It adds specificity beyond the tool name and makes the subject matter unambiguous, even though it is phrased as a noun phrase rather than a verb phrase.

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 guidance on when to use this tool, no prerequisites, and no mention of alternatives (though none exist). The description simply names the data category without explaining what situations call for it or how it relates to other possible retrieval tools.

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

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev0.1.8
    • First observedget_creative_goods_trade
Deploy Server
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

TDQS

B3/5.0

Scored across 1 tool

Disambiguation5/5

There is only one tool, so there is no possibility of confusion between overlapping tools. The single tool's purpose is clearly defined around Hong Kong creative goods trade data, making selection unambiguous.

Naming Consistency5/5

The tool name follows a clear verb_noun pattern ('get_creative_goods_trade'), which is consistent with common naming conventions. With a single tool, there are no conflicting styles to evaluate, so consistency is perfect by default.

Tool Count3/5

A single tool feels thin for a server dedicated to Hong Kong creative goods trade, as it likely serves a narrow niche. However, the tool is not trivial—it addresses a specific data need—so the count is borderline rather than extremely mismatched.

Completeness2/5

The tool surface appears significantally incomplete: it offers a single access point for exports, re-exports, and imports without evident filtering, time-series, or aggregation capabilities. Agents would likely need additional tools to analyze trends, compare categories, or query specific years, which are absent from this server.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • hk-housing-mcp-server

    hkopenai
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables querying Hong Kong private storage statistics such as completions, stock, and vacancy data via a FastMCP interface, sourced from the Rating and Valuation Department.
    1
    MIT

  • Hong Kong Government

    hkopenai
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides access to government development, geography and land information data through a FastMCP interface, including data on new building plans processed by the Building Authority.
    1
    MIT