Skip to main content
Glama
Sign In

Bnm My

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Bnm Endpoint

bnm_endpoint
Read-onlyIdempotent

Call any other confirmed Bank Negara Malaysia public endpoint by path and get its raw data. Confirmed live paths: "interest-rate" (interbank/money-market deposit rates by tenor), "interest-volume" (transaction volumes by tenor), "islamic-interbank-rate", "kl-usd-reference-rate" (KL USD/MYR reference rate), "usd-interbank-intraday-rate" (intraday hi/lo). Also accepts the documented sub-path forms (e.g. "exchange-rate/USD", "opr/year/2025") if you need a path not covered by a dedicated tool.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "path": "interest-rate"
    },
    "name": "bnm_endpoint"
  }
}

Input Schema

NameRequiredDescriptionDefault
pathYesEndpoint path under https://api.bnm.gov.my/public/ — e.g. "interest-rate", "islamic-interbank-rate", "kl-usd-reference-rate". No leading slash needed.
queryNoOptional query parameters as key/value pairs, e.g. {"session":"1130","quote":"rm"}.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {
+    "path": "interest-rate"
+  },
+  {
+    "path": "exchange-rate/USD",
+    "query": {
+      "quote": "fx",
+      "session": "1700"
+    }
+  }
+]
  2. First observed

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already provide readOnly, openWorld, idempotent, and non-destructive hints. The description adds detail about returning raw data and confirmed live paths, which aids reliability without contradicting annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is a single paragraph, efficiently stating purpose, examples, and usage notes. It front-loads the core action and provides necessary detail without verbosity.

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's role as a catch-all for BNM endpoints, the description covers base URL, valid paths, and query parameter usage. It lacks specifics on error behavior or rate limits, but annotations and sibling context reduce the need for such details.

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 has 100% coverage with descriptions for both path and query. The description adds concrete examples (e.g., interest-rate, exchange-rate/USD) and clarifies formatting (no leading slash), enhancing clarity 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 calls any confirmed BNM public endpoint by path and returns raw data. It lists multiple specific paths (e.g., interest-rate, kl-usd-reference-rate) and distinguishes itself from dedicated tool siblings.

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?

Explicitly says to use this tool for paths not covered by a dedicated tool, e.g., 'if you need a path not covered by a dedicated tool.' Provides confirmed live paths as examples, but does not explicitly state when not to use it or list alternatives.

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

All Bnm My 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