Skip to main content
Glama

indonesia_crypto_idr

Read-only

Paid $0.05 per call: crypto prices in Indonesian rupiah from Indodax — last trade, bid, ask, 24h high/low and rupiah volume for up to 8 symbols. The domestic IDR market, including any local premium.

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": "indonesia_crypto_idr"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoComma-separated tickers, e.g. 'btc,eth,usdt'. Up to 8.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover the read-only safety profile, so the description earns credit for adding genuinely new context: a $0.05 per-call cost and the specific venue (Indodax) plus the local-premium caveat. It still doesn't say what happens when the optional symbols parameter is omitted or whether results are partial when a ticker is unknown.

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?

Two short units, front-loaded with the resource and cost, both of which drive decision-making. The trailing fragment about the domestic market earns its place by differentiating from the FX tool, though it could have been folded into the main sentence.

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 one optional param, no output schema, and readOnlyHint supplied, the description does the heavy lifting by listing the return fields and disclosing cost. The only real omission is default/empty-argument behavior, which matters because no parameters are required.

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 single parameter is already fully documented including format and the 8-symbol limit. The description's 'up to 8 symbols' merely restates the schema without adding format, default, or error 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?

Names the resource precisely (crypto prices in IDR from Indodax) and enumerates the returned fields (last trade, bid, ask, 24h high/low, rupiah volume) with a symbol cap. The closing clause about 'the domestic IDR market, including any local premium' implicitly separates it from the FX sibling, though no sibling is named outright.

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 only implied by the subject matter — an agent infers 'call this when you need IDR crypto quotes.' There is no explicit when-not guidance, no mention of when to prefer a different endpoint, and no statement about behavior with zero symbols supplied despite 0 required params.

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.

Resources