Skip to main content
Glama
Sign In

Hkma Hk

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Hkma Monetary Base

hkma_monetary_base
Read-onlyIdempotent

Daily figures for the components of the Hong Kong Monetary Base: Certificates of Indebtedness, government notes & coins in circulation, aggregate balance (before/after discount window), and outstanding Exchange Fund Bills & Notes. One record per business day. Use from/to to window the dates.

Input Schema

NameRequiredDescriptionDefault
toNoEnd of date window, YYYY-MM-DD (or YYYY-MM for monthly series), e.g. "2026-01-31".
fromNoStart of date window, YYYY-MM-DD (or YYYY-MM for monthly series), e.g. "2026-01-01".
langNoLanguage of text fields: "en" (default), "tc", or "sc". Required by some datasets (e.g. coin-cart-schedule).
fieldsNoComma-separated subset of columns to return, e.g. "end_of_date,hibor_overnight".
offsetNoZero-based record offset for pagination.
sortbyNoColumn to sort by, e.g. "end_of_date".
pagesizeNoRecords per page (default ~100). Max varies by dataset.
sortorderNoSort direction: "asc" or "desc".

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "from": "2024-01-01",
+    "to": "2024-12-31"
+  }
+]
  2. Added

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already cover readOnlyHint, openWorldHint, idempotentHint, and destructiveHint. The description adds behavioral context by listing the specific components included and stating it returns daily figures. This provides useful details beyond annotations, though no additional safety or side-effect information is needed given the 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?

The description is a single sentence that efficiently conveys the tool's purpose, components, frequency, and usage. It is front-loaded and contains no unnecessary words, making it highly concise and well-structured.

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?

Given the tool has 8 parameters, no output schema, and rich annotations, the description covers the core data content and date windowing. It does not mention default fields or pagination behavior, but these are addressed by the schema. The description is sufficient for understanding the tool's primary functionality.

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 the baseline is 3. The description mentions 'from' and 'to' but does not add new semantics beyond the schema's parameter descriptions. It does not clarify the meaning of other parameters like 'fields', 'offset', or 'pagesize' beyond what is in 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 it provides 'Daily figures for the components of the Hong Kong Monetary Base' and lists specific components (Certificates of Indebtedness, etc.), making the tool's purpose highly specific. It distinguishes this tool from siblings like 'hkma_exchange_rates' or 'hkma_interbank_interest_rates' by focusing on monetary base components.

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 explicitly says 'Use from/to to window the dates,' giving direct guidance on parameter usage. It also notes 'One record per business day,' setting expectations for data frequency. However, it does not compare this tool to other HKMA tools or specify when to choose this over alternatives, which is a minor gap.

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

All Hkma Hk 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