Skip to main content
Glama

Censtatd Hk

by io.github.pipeworx-io

Censtatd Search Tables

censtatd_search_tables
Read-onlyIdempotent

Search the Hong Kong C&SD table catalogue by keyword (e.g. 'exchange rates', 'unemployment', 'merchandise trade') and get back matching table ids + titles to use with censtatd_get_table. Backed by the data.gov.hk open-data index of C&SD tablechart datasets. Note: not every C&SD table is indexed there; ids can also be read off the table URL on data.censtatd.gov.hk (the '310-31001' part of web_table.html?id=310-31001).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 20, max 50).
queryYesKeywords, e.g. 'exchange rates' or 'employment earnings'.

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already convey that the tool is read-only, open-world, idempotent, and non-destructive. The description adds valuable behavioral context: it searches an external index, coverage is incomplete, and it provides an alternative method to obtain IDs. This is useful beyond the annotations, though the annotations already handle the safety profile.

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 extremely concise: two sentences with no unnecessary words. The first sentence delivers the core purpose and examples, the second adds important context (coverage limitation and alternative). Every part earns its place, and the structure is front-loaded for quick understanding.

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?

Given the tool's simplicity (search with text query, returns IDs and titles), and no output schema, the description adequately sets expectations. It explains what the tool returns, its limitations (incomplete coverage), and how to find missing IDs. This is complete for an agent to decide when and how to use it.

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%, so baseline is 3. The description adds meaningful context: it explains how to use the query parameter with examples ('exchange rates'), clarifies the limit parameter's default and maximum, and mentions the data source ('backed by the data.gov.hk open-data index'), which adds value 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's purpose: searching the Hong Kong C&SD table catalogue by keyword to retrieve matching table IDs and titles for use with censtatd_get_table. It provides specific examples of keywords and distinguishes itself from sibling tools (censtatd_get_table, censtatd_table_info) by positioning this as the search step.

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

Usage Guidelines5/5

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

The description explicitly states when to use this tool (to search by keyword) and provides a when-not scenario: not every C&SD table is indexed, and offers an alternative method (reading IDs from the URL). It also explains the data source (data.gov.hk open-data index), giving agents clear context for decision-making.

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

All Censtatd Hk toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4/5.0
Disambiguation4/5

Most tools target a distinct action or resource, and the long routing descriptions make choices like ask_pipeworx vs ask_pipeworx_grounded vs deep_research clear. The main weak spots are ask_pipeworx_beta being currently identical to ask_pipeworx and the six overlapping Polymarket tools, but each has a discernible workflow.

Naming Consistency3/5

Naming has internally consistent subfamilies such as censtatd_*, ask_pipeworx*, and polymarket_*, but overall it mixes verb-first names (get_table, validate_claim, subscribe), noun-first names (entity_profile, bet_research, pipeworx_feedback), and bare imperatives (remember, forget, recall). The set is readable but does not follow one convention.

Tool Count2/5

35 tools exceeds the 25+ threshold and feels heavy, especially since many tools (generate_llms_txt, scan_dependency, pipeworx_feedback, pipeworx_trending) are unrelated to the HK Census core implied by the server name. The broad Pipeworx scope explains the width, but the surface is still large for an agent to navigate efficiently.

Completeness4/5

For a read-only research/data-access gateway, coverage is strong: generic lookup, grounded verification, deep research, entity profile/compare/change, entity resolution, memory, and subscription lifecycle are all represented. Minor gaps exist, such as no subscription update, no explicit bulk/export path, and fewer HK C&SD convenience wrappers, but agents can work around them.

Resources