Skip to main content
Glama

Primary Sources

by io.github.simonmak-ascent
OverviewDiscussionsAdmin

hkma

Read-onlyIdempotent

Call the Hong Kong Monetary Authority public API (free, no key). Pass an HKMA data path to retrieve monetary, banking or market statistics as JSON. Use for HK monetary/liquidity data; use world_bank_indicator for development indicators.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pathYesHKMA path, e.g. market-data-and-statistics/daily-monetary-statistics/daily-figures-interbank-liquidity
paramsNoOptional query parameters

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
dataYesSource payload; fields vary per tool
sourceYesHuman-readable upstream source name
retrievedAtYesISO-8601 timestamp of retrieval

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / params / description
      Added value: +"Optional query parameters"
    • addedInput schema / properties / path / description
      Added value: +"HKMA path, e.g. market-data-and-statistics/daily-monetary-statistics/daily-figures-interbank-liquidity"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "properties": {
+    "data": {
+      "description": "Source payload; fields vary per tool",
+      "type": "object"
+    },
+    "retrievedAt": {
+      "description": "ISO-8601 timestamp of retrieval",
+      "type": "string"
+    },
+    "source": {
+      "description": "Human-readable upstream source name",
+      "type": "string"
+    }
+  },
+  "required": [
+    "source",
+    "retrievedAt",
+    "data"
+  ],
+  "type": "object"
+}
  2. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely new context that annotations cannot express: the API is free and requires no key, which affects how the agent should handle auth failures. It does not discuss rate limits or error behavior.

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 compact sentences, zero filler, with the core action and the routing alternative both front-loaded. Every sentence earns its place.

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?

With an output schema present, the description needn't explain return values, and it notes the response is JSON. Annotations plus schema plus the no-key note cover most of what an agent needs; only edge-case behavior (invalid paths, rate limits) is unaddressed.

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 coverage is 100%, so both parameters (path, params) are already documented with an example path. The description restates that a path must be passed but adds no format, encoding, or query-parameter syntax beyond the schema. Baseline 3 applies when the schema carries the load.

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 (call) and resource (Hong Kong Monetary Authority public API) and names the data scope (monetary, banking, market statistics as JSON). It explicitly differentiates itself from world_bank_indicator, so an agent can route without opening either schema.

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 context ('Use for HK monetary/liquidity data') and names an alternative with the condition that selects it ('use world_bank_indicator for development indicators'). Lacks explicit when-not-to-use guidance beyond that single contrast, but the routing signal is unambiguous.

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

All Primary Sources toolsInspect
Try in Browser
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

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources