Skip to main content
Glama
zenith-sb-mcp

zenith-sb-mcp

quote

Read-only

Retrieve real-time IDX market data for a ticker or index, including last price, change, best bid/offer, and internal company ID resolution.

Instructions

Real-time quote for an IDX symbol: last price, change, and best bid/offer. Also resolves the symbol's internal company id.

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": {
      "symbol": "<symbol>"
    },
    "name": "quote"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesIDX ticker, e.g. BBRI, or index e.g. IHSG

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so the description's added value is the real-time freshness of the data and the non-obvious side effect that it also resolves the symbol's internal company id. It stops short of noting failure behavior for invalid tickers or rate limits, but the extra context is genuinely useful.

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

Conciseness5/5

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

Two short sentences with the primary purpose front-loaded and the secondary return value appended. Nothing is redundant or buried.

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?

For a one-parameter read tool with a full schema and no output schema, the description enumerates the meaningful return fields and the freshness of the data, which is enough to call it correctly. Minor gaps remain around error handling for unrecognized symbols.

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% and the single parameter already documents 'IDX ticker, e.g. BBRI, or index e.g. IHSG', including the index case. The description's phrase 'IDX symbol' adds no meaning beyond that, so the baseline of 3 for schema-covered parameters applies.

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 names a specific verb and resource ('Real-time quote for an IDX symbol') and enumerates the returned fields (last price, change, best bid/offer), plus a secondary purpose of resolving the internal company id. It is clear on its own, though it never distinguishes itself from adjacent siblings such as intraday_prices or orderbook.

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 'Real-time quote' — an agent can infer it is for current price checks rather than historical series, but there is no explicit when-to-use, when-not-to-use, or named alternative. No prerequisites or call ordering are stated.

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