Skip to main content
Glama

Hongkong Procurement

by io.github.pipeworx-io
OverviewAdmin

Hk Search Awards

hk_search_awards
Read-onlyIdempotent

Search recently AWARDED Hong Kong government procurement contracts from the Government Logistics Department (GLD) "Contracts Awarded" open dataset (data.gov.hk, English). Returns each award with tender reference, subject/particulars, contractor, contract amount in HK$, and award date. Pass an optional query to filter by substring across subject, contractor, tender reference, and department (case-insensitive); omit query to list the most recent awards. Use for questions like "who won the HK water treatment contract", "Hong Kong government security guard contract awards", or "recent GLD contracts to ".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of awards to return. Default 25, max 100.
queryNoOptional case-insensitive substring to filter awards by subject/particulars, contractor name, tender reference, or department (e.g. "security guard", "Water Supplies Department", "Zung Fu"). Omit to list all current awards.

Schema Changelog

Changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "query": "security guard"
+  },
+  {
+    "limit": 50,
+    "query": "Water Supplies Department"
+  }
+]
  2. First observed

TDQS

A4.4/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds valuable behavioral details: case-insensitive substring filtering across multiple fields, and the specific output fields returned. It does not contradict annotations.

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?

Three sentences, front-loaded with the main purpose, then output details, then usage guidance. Every sentence is informative, no redundancy.

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?

The description covers data source, returned fields, filtering behavior, and provides examples. For a simple lookup tool with no output schema, this is comprehensive. One minor gap: no mention of data freshness beyond 'recently', but the award date field mitigates this.

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%, but the description adds meaning by specifying which fields are searched by the query parameter (subject, contractor, tender reference, department). This goes beyond the schema's 'substring filter' phrasing. Default and max for limit are already in 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 explicitly states it searches recently awarded Hong Kong government procurement contracts from the GLD dataset, specifies the returned fields, and gives usage examples. The verb 'search' and resource 'awards' are clear, and no sibling tool competes directly, so distinction is implicit.

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 clearly indicates when to use with or without a query, and provides example questions. It does not explicitly state when not to use or list alternatives, but given no similar tools, the guidance is sufficient.

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

All Hongkong Procurement 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.

Resources