Skip to main content
Glama

FiLot: gold prices and gold bar records

Indonesian gold buyback prices for one bar

gold_buyback_prices
Read-onlyIdempotent

What Indonesian dealers pay today to buy back ONE gold bar of a given brand and weight, in rupiah: the highest price that fits every bar of that brand and size, prices that fit only some bars (for example Antam made in 2026), each with dealer and day, and a world-gold-price estimate when no dealer FiLot reads prices the brand. Brands with dealer prices: Antam (Logam Mulia), UBS, Lotus Archi, Galeri 24, Sampoerna; any other brand (King Halim, PAMP, Argor-Heraeus, ...) gets the estimate and Galeri 24's Sentra Buyback line. It also sets the highest dealer price beside the world value of the gold (how far below or above it sits), and an offer someone made for the bar when one is given.

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": {
      "brand": "<brand>",
      "grams": "<grams>"
    },
    "name": "gold_buyback_prices"
  }
}

Input Schema

NameRequiredDescriptionDefault
langNoAnswer language: id = Bahasa Indonesia, en = English (default).
brandYesBrand stamped on the bar, e.g. Antam, UBS, Lotus Archi, Galeri 24, Sampoerna, King Halim, PAMP.
gramsYesWeight of ONE bar in grams (1 troy ounce = 31.1 g; 1 kg = 1000).
offer_idrNoOptional. A price in rupiah that someone offered to pay for this bar. The answer sets it beside what dealers pay today and the world value of the gold: numbers only, no advice.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • addedInput schema / properties / offer_idr
      Added value: +{
      +  "description": "Optional. A price in rupiah that someone offered to pay for this bar. The answer sets it beside what dealers pay today and the world value of the gold: numbers only, no advice.",
      +  "maximum": 10000000000000,
      +  "minimum": 1000,
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety bar is low; the description adds genuinely useful behavior: a brand-coverage list, a documented fallback (estimate plus Galeri 24 Sentra Buyback line) for unlisted brands, partial-fit price handling, and an explicit 'numbers only, no advice' stance on offer_idr. It stops short of describing ordering, currency rounding, or what happens when a brand/size has zero matches.

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

Conciseness3/5

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

Content is dense and mostly earns its place, but it is delivered as a single ~110-word run-on sentence with nested parentheticals and a mid-sentence clause shift ('and a world-gold-price estimate when no dealer FiLot reads prices the brand'), which is hard to parse on first read. Bullet-like structure would serve this complexity far better.

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?

With no output schema, the description carries the return-value burden and does so: best fitting price, partially-fitting prices, dealer and day, world-value comparison, and offer comparison. What remains missing is the shape of the response for a brand/size with no data at all.

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 description coverage is 100%, so the baseline is 3. The description reinforces the key semantic that grams is the weight of exactly ONE bar and enumerates brands, but adds no syntax or format detail beyond what the schema already documents.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: what Indonesian dealers pay today to buy back ONE bar of a given brand and weight, in rupiah. That is enough to separate it from gold_price_on_date (asking/spot price) and world_gold_price, but no sibling is named, so the routing is left to inference.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implicitly defines the use case (valuing a bar someone wants to sell) and describes which brands get real dealer quotes versus the FiLot/world estimate fallback. However, it never states when to pick this over gold_price_on_date or verify_gold_bar_record, nor any prerequisites, so guidance is implied rather than explicit.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.