Skip to main content
Glama
Sign In

Bnm My

by io.github.pipeworx-io
OverviewDiscussionsAdmin

Bnm Gold Kijang Emas

bnm_gold_kijang_emas
Read-onlyIdempotent

Kijang Emas — Malaysia's official gold bullion coin — buying and selling prices (in MYR) by coin size (one_oz, half_oz, quarter_oz). Latest prices by default, or every effective date within a given year+month.

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_gold_kijang_emas"
  }
}

Input Schema

NameRequiredDescriptionDefault
yearNoFour-digit year, e.g. 2026. Provide together with "month" for a historical month.
monthNoMonth 1-12. Requires "year".

Schema Changelog

Changes observed during successful MCP inspections.

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

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false. The description adds that prices are in MYR, by coin size, and that latest prices are returned by default or historical per year+month. No contradiction.

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?

Two sentences: first defines what is returned, second explains default vs historical. Front-loaded, no waste, every sentence earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema; the description does not explain return structure (e.g., format of prices per coin size). Could be improved by specifying whether buying/selling prices are separate fields or showing an example.

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% with descriptions for year and month. The description reinforces that without parameters gives latest prices, adding slight value but not significantly beyond 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 returns buying and selling prices of Kijang Emas gold coins in MYR by coin size. It specifies default latest prices or historical with year+month, distinguishing it from sibling BNM tools like bnm_exchange_rates.

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 implicitly indicates use for gold coin prices, but does not explicitly state when not to use it or mention alternatives like bnm_exchange_rates. However, the context of sibling tools makes it clear.

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