Skip to main content
Glama

FiLot: gold prices and gold bar records

Gold price on a past date

gold_price_on_date
Read-onlyIdempotent

The gold price on a past date, for records such as a tax return, an inheritance or a purchase: the world price of fine gold in any currency (FiLot's own daily record, kept since 22 Oct 2026: the day's last reading) and, for Indonesia, the dealers' Antam buyback price that day (stored since 25 Sep 2026). Signed, with a link to check it. A record of the price, not advice.

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

Input Schema

NameRequiredDescriptionDefault
dateYesThe day (YYYY-MM-DD, Jakarta date).
langNoAnswer language: id = Bahasa Indonesia, en = English (default).
currencyNoThree-letter currency code for the world price. Default USD.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already cover safety (readOnly, idempotent, non-destructive). The description adds valuable context beyond annotations: data availability start dates (22 Oct 2026 for world price, 25 Sep 2026 for Antam buyback), the fact that the world price reflects 'the day's last reading', and that the result is 'signed, with a link to check it'. This gives the agent useful expectations about output provenance and limitations.

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?

The description is a single long sentence with nested parentheticals, which makes it somewhat dense. The core purpose is front-loaded, but phrases like 'for records such as a tax return, an inheritance or a purchase' and 'A record of the price, not advice' add length without much operational value. It could be more structured for easier parsing.

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 burden of explaining return values, and it does so adequately: world price in any currency, Antam buyback for Indonesia, signed with a verification link, plus data coverage dates. It lacks exact output format details but provides enough context for an agent to understand what it will get.

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 schema already documents all three parameters thoroughly. The description mentions 'any currency' (aligning with the currency parameter) and 'for Indonesia' (hinting at the Antam buyback data), but adds no syntax, format, or behavioral details beyond what the schema provides. Baseline 3 is appropriate.

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?

The description clearly states the resource (gold price on a past date) and the specific data returned (world price in any currency, plus Indonesia Antam buyback). It distinguishes itself from current-price siblings by emphasizing 'past date', though it does not name any alternative tool explicitly.

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?

Usage is implied by 'on a past date' and 'for records such as a tax return, an inheritance or a purchase', but there is no explicit guidance on when to use this versus siblings like world_gold_price or gold_buyback_prices. The agent must infer that this is for historical lookups rather than current prices.

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.