SiteCheck Crypto & Finance

IndexMundi monthly commodity price table for one commodity

finance_indexmundi

Read-only

IndexMundi monthly commodity price table for one commodity (default gold), read from the public commodity page: month and price as IndexMundi publishes them. Prices are as shown on the page; units follow that page. Related tools on this server, for a different need: finance_bstock when you need B-Stock wholesale liquidation auctions: total live lots; finance_coingecko when you need CoinGecko spot prices for up to 10 coins in one currency. Price: $0.002 in USDC per successful call, paid with x402 (Base, Solana or Arc); failed calls are not charged.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "finance_indexmundi"
  }
}

Input Schema

Name	Required	Description	Default
`months`	No	How many latest months, 1 to 60 (default 12)
`commodity`	No	IndexMundi commodity slug, e.g. gold, crude-oil

Output Schema

Name	Required	Description	Default
`rows`	No
`source`	No
`checkedAt`	No
`commodity`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 23, 2026

TDQS

A3.6/5.0

Behavior4/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context beyond that: units follow the source page rather than being normalized, values are as published, and each successful call costs $0.002 USDC via x402 on Base/Solana/Arc while failures are free. It does not describe latency or failure modes, but the cost and unit caveats are the high-value disclosures.

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 core sentence is front-loaded and tight, but the middle 'Related tools on this server' clause consumes substantial space routing to two tools that are not real alternatives for commodity prices, and the payment boilerplate is verbose. Against a 100+ sibling list, that routing sentence does little work.

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?

An output schema exists, so return fields need no explanation, and the description covers the source, unit caveat, default commodity, and cost. What remains thin is guidance on picking a commodity slug from the IndexMundi namespace and whether the tool errors on unknown slugs, which matters for a slug-driven scraper.

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 coverage is 100%, so both parameters are already documented with ranges and an example slug. The one thing the description adds is that the commodity defaults to gold, which the schema does not state, but it adds nothing about slug format or whether the 1–60 month cap is validated server-side. Baseline 3 is appropriate when the schema carries the parameter semantics.

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 states a specific verb and resource: read the IndexMundi monthly commodity price table for one commodity, returning month and price. It also notes the default commodity (gold) and the public-page source. It does not distinguish itself from the many other price/commodity sources on this server (e.g. finance_alpha_vantage_public, finance_world_bank), naming instead two siblings that serve unrelated needs.

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 guidance is present only in inverted form: it tells the agent when to use finance_bstock and finance_coingecko instead, but never states when this tool is the right choice or when to avoid it. The default of gold is implied as the zero-config case, but there is no guidance on choosing a commodity slug or month count.

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

All SiteCheck Crypto & Finance 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?