Lordevo Shop (x402 website checks)

Malaysian ringgit exchange rates + OPR (Bank Negara Malaysia data) ($0.002/call)

myr_rates

Read-onlyIdempotent

$0.002 per call (x402, USDC on Base; free trial: add "trial": true or use try_free). [Data utilities] Bank Negara Malaysia exchange rates against the ringgit (buying, selling, middle; MYR per unit) for one currency or ALL, plus the current Overnight Policy Rate. Source: Bank Negara Malaysia; data subject to the Terms of Use for BNM Datasets; not endorsed by BNM. Cached 15 min. ~0.5-2 s.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "currency": "<currency>"
    },
    "name": "myr_rates"
  }
}

Input Schema

Name	Required	Description	Default
`trial`	No	Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms.
`currency`	Yes	3-letter currency code to price in ringgit, e.g. USD, SGD or EUR, or ALL for every currency BNM publishes

Output Schema

Name	Required	Description
`base`	No
`tool`	No
`cache`	No
`rates`	No
`_trial`	No	Present when the call was a free trial call.
`session`	No
`currency`	No
`provider`	No
`price_usd`	No
`attribution`	No
`overnight_policy_rate`	No

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedNov 5, 2026

changedInput schema / properties / trial / description

Previous value: -"Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms."New value: +"Optional. true = free if a trial call is left (3 per IP per UTC day), else the payment terms."

Changed1 schema field changedNov 3, 2026

changedInput schema / properties / currency / description

Previous value: -"3-letter currency code (e.g. USD, SGD, EUR) or ALL"New value: +"3-letter currency code to price in ringgit, e.g. USD, SGD or EUR, or ALL for every currency BNM publishes"

Changed2 schema fields changedNov 3, 2026

addedInput schema / properties / trial

Added value: +{
+  "description": "Optional. true = answer free if a trial call is left (3 per IP per UTC day); otherwise you get the payment terms.",
+  "type": "boolean"
+}

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "anyOf": [
+    {
+      "required": [
+        "tool",
+        "rates",
+        "attribution"
+      ]
+    },
+    {
+      "properties": {
+        "accepts": {
+          "type": "array"
+        },
+        "error": {
+          "type": "string"
+        },
+        "resource": {
+          "type": "object"
+        },
+        "x402Version": {
+          "type": "integer"
+        }
+      },
+      "required": [
+        "x402Version",
+        "accepts"
+      ]
+    },
+    {
+      "properties": {
+        "charged": {
+          "type": "boolean"
+        },
+        "error": {
+          "type": "string"
+        },
+        "message": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "error"
+      ]
+    }
+  ],
+  "properties": {
+    "_trial": {
+      "description": "Present when the call was a free trial call.",
+      "type": "object"
+    },
+    "attribution": {
+      "type": "string"
+    },
+    "base": {
+      "type": "string"
+    },
+    "cache": {
+      "type": "object"
+    },
+    "currency": {
+      "type": "string"
+    },
+    "overnight_policy_rate": {
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "price_usd": {
+      "type": "number"
+    },
+    "provider": {
+      "type": "string"
+    },
+    "rates": {
+      "items": {
+        "properties": {
+          "buying": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "currency": {
+            "type": "string"
+          },
+          "date": {
+            "type": [
+              "string",
+              "null"
+            ]
+          },
+          "middle": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "myr_per_1": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "myr_per_1_basis": {
+            "type": "string"
+          },
+          "selling": {
+            "type": [
+              "number",
+              "null"
+            ]
+          },
+          "unit": {
+            "type": "number"
+          }
+        },
+        "type": "object"
+      },
+      "type": "array"
+    },
+    "session": {
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "tool": {
+      "type": "string"
+    }
+  },
+  "type": "object"
+}

AddedOct 26, 2026

TDQS

A4.4/5.0

Behavior4/5

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

Annotations already declare a read-only, idempotent, non-destructive open-world call, so the description's remaining job is to add operational context, which it does: $0.002 per call via x402 USDC on Base, 15-minute cache, and ~0.5-2 s latency. The licensing caveat (BNM Terms of Use, not endorsed by BNM) is a genuinely useful disclosure for downstream attribution, though it doesn't say what happens on an invalid currency code.

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?

Dense but tightly packed with no filler, and the cost/trial notice is front-loaded so a cost-sensitive agent sees pricing before anything else. The tradeoff is that the actual data purpose sits behind a bracketed tag and a long run-on sentence, which slightly hurts skimmability.

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?

With an output schema present, the description needn't explain return values, and it still covers the things structured fields can't: pricing model, cache TTL, latency, trial quota, and data provenance/terms. Nothing an agent needs to decide to call this tool is missing.

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%, so the parameters are already documented, but the description adds real meaning beyond the schema: the returned rates are quoted as MYR per unit with buying/selling/middle variants, which clarifies output semantics, and the trial flag's free-call allowance is restated at the top. That extra framing lifts it above the baseline 3.

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?

Names a specific resource and verb: Bank Negara Malaysia exchange rates against the ringgit (buying, selling, middle; MYR per unit) for one currency or ALL, plus the current Overnight Policy Rate. No sibling tool covers FX or policy rates, so the purpose is unambiguous and self-distinguishing from the rest of the catalog.

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 for when the tool applies (FX conversion into MYR, OPR lookup, single currency vs ALL) and routes free usage to a named sibling (try_free) as an alternative to the trial flag. It stops short of explicit when-not-to-use guidance, so it falls short of a 5.

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

All Lordevo Shop (x402 website checks) tools Inspect

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

Need Help?