Skip to main content
Glama

Kobo Terminal NGX

Index history

get_index_history
Read-onlyIdempotent

Daily closing levels for any NGX index, including the full All-Share Index history. Plan: Free+.

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": {
      "code": "<code>"
    },
    "name": "get_index_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoEnd date, YYYY-MM-DD. Example: 2026-11-18
codeYesIndex code or slug. Example: ASI
fromNoStart date, YYYY-MM-DD. Example: 2025-01-01

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds two genuine pieces of context beyond that: the plan gate ('Plan: Free+') and the guarantee that full All-Share Index history is available. It says nothing about pagination, default date range, rate limits, or result ordering.

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, front-loaded with the capability and followed by the access tier. No filler, no restatement of the title, and each sentence contributes distinct information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple read-only history tool with a fully documented schema and no output schema, the core need is covered. The gap is that from/to are optional per the schema but the description never states what happens without them — a default window, full history, or an error — which materially affects how an agent calls it.

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%, with code, from and to each documented including format and examples, so the schema carries parameter meaning. The description only echoes 'any NGX index' (mapping to code) and adds no detail on how from/to behave when omitted, which is the one parameter question the schema leaves open.

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 resource and data shape: daily closing levels for NGX indices, with the All-Share Index called out explicitly. 'Daily closing levels' implicitly separates it from the sibling get_index_intraday, but no sibling is named, so the differentiation is inferential rather than explicit.

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 the phrase 'daily closing levels' — an agent can infer this is the historical end-of-day series rather than a snapshot or intraday feed. However, there is no explicit when-to-use statement, no exclusion, and no named alternative (e.g., get_index_intraday or get_index) for the cases this tool does not cover.

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