Skip to main content
Glama
Sign In

Bnm My

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Bnm Policy Rate Opr

bnm_policy_rate_opr
Read-onlyIdempotent

Overnight Policy Rate (OPR) — Bank Negara Malaysia's benchmark monetary policy interest rate. Latest OPR decision by default, or every decision in a given year (with change_in_opr and new_opr_level).

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": {},
    "name": "bnm_policy_rate_opr"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFour-digit year, e.g. 2025. Omit for the latest OPR level.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
+  {},
+  {
+    "year": 2025
+  }
+]
  2. Added

TDQS

A4.6/5.0
Behavior4/5

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

The description adds behavioral context beyond annotations by stating the default behavior (latest decision) and the additional fields returned when a year is specified ('change_in_opr', 'new_opr_level'). No contradictions with 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 two concise sentences, front-loading the core purpose and then explaining the parameter's effect. No redundant information.

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 simple tool with one optional parameter and no output schema, the description fully covers the needed context: default behavior, optional year, and what data is returned. It is complete for an agent to invoke correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The description adds significant meaning to the year parameter: omitting it returns the latest OPR level, while including it returns every decision for that year with change and new level. This goes beyond the schema's description, which only defines the parameter as 'Four-digit year'.

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 identifies the tool as retrieving Overnight Policy Rate (OPR) decisions from Bank Negara Malaysia, specifying the resource (OPR) and action (retrieve). It distinguishes from sibling tools like 'bnm_base_rate' by explicitly naming OPR and referencing benchmark monetary policy.

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 provides clear context: default returns the latest OPR decision, while providing a year returns all decisions for that year with change and new level. It does not explicitly state when not to use it, but the context is sufficient for a simple retrieval tool.

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