Skip to main content
Glama

Kobo Terminal NGX

Index intraday

get_index_intraday
Read-onlyIdempotent

Today's intraday points for an index (level, change, value and volume traded) plus the latest live reading. 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_intraday"
  }
}

Input Schema

NameRequiredDescriptionDefault
codeYesIndex code. Example: ASI

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, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that by listing the exact payload contents and, importantly, the 'Plan: Free+' entitlement requirement, which affects whether the call can succeed at all. It omits intraday granularity (sampling interval, point count) and how the 'latest live reading' relates to the point series.

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 compact sentences: the payload contents come first, then the plan requirement. Every clause carries information and nothing is padded or repeated from the title.

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 no output schema, the description usefully enumerates the returned fields, and with a single trivially-documented parameter the input story is complete. The main remaining gap is behavioral detail about the intraday series itself — sampling frequency, session boundaries, and whether the live reading is a separate item or the last point.

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?

There is a single required parameter with 100% schema description coverage (including an 'ASI' example), so the baseline is 3. The description adds no further meaning about the index code format, case sensitivity, or what happens with an invalid or delisted code.

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 verb and resource — 'today's intraday points for an index' — and enumerates the returned fields (level, change, value, volume, latest live reading), which cleanly separates it from get_index_history (past data) and get_index (presumably a snapshot). It stops short of naming a sibling to disambiguate against, keeping it at 4 rather than 5.

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 word 'today's' implies the temporal scope and thus when to reach for this over a historical endpoint, but there is no explicit when-to-use/when-not-to-use statement and no named alternative. The reader must infer the routing from context.

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