Skip to main content
Glama

Kobo Terminal NGX

All NGX indices

list_indices
Read-onlyIdempotent

All 21 NGX indices: ASI, NGX30, NGX Premium, NGX Pension, Banking, Insurance, Consumer Goods, Oil & Gas, Industrial, Lotus Islamic, ASeM and more, with week, month, year and inception change. Plan: Free+.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so safety is covered. The description adds genuinely new context: the entitlement requirement ('Plan: Free+') and the presence of multi-period change figures in the payload, which tells the agent what analysis it can do without a follow-up call. No mention of pagination, but 21 records makes that a non-issue.

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?

A single front-loaded sentence that leads with the scope ('All 21 NGX indices') before the enumeration. The 12-name example list is somewhat long given 'and more' follows, but it usefully telegraphs the index universe the agent will receive.

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?

No output schema exists, so the description carries the burden of describing return content, which it does by naming the change horizons (week, month, year, inception). Combined with the zero-parameter signature and the read-only annotations, an agent has enough to call this correctly; only explicit sibling routing is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description correctly implies a no-argument call by describing a fixed complete listing.

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 (all 21 NGX indices), enumerates representative examples (ASI, NGX30, Banking, Insurance, ASeM), and specifies the metrics returned (week, month, year, inception change). It does not explicitly distinguish itself from siblings like get_index or get_index_history, so an agent must infer that this is the catalog/listing endpoint rather than a single-index lookup.

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?

The phrase 'All 21 NGX indices' implies the use case is browsing the full index catalog, and 'Plan: Free+' signals availability. However, there is no explicit statement of when to use this versus get_index or get_index_history, and no exclusions are given.

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