Skip to main content
Glama

Kobo Terminal NGX

Price history (OHLCV)

get_price_history
Read-onlyIdempotent

Daily open, high, low, close and volume for one NGX stock, from May 2000 to today. Plan: Free+. Free keys get the last 7 days. Starter and above get the full daily history back to May 2000.

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

Input Schema

NameRequiredDescriptionDefault
toNoEnd date, YYYY-MM-DD. Example: 2026-11-18
daysNoMost recent N trading days. Example: 30
fromNoStart date, YYYY-MM-DD. Example: 2020-01-01
symbolYesNGX ticker. Example: DANGCEM

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/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 genuinely behavioral information beyond that: the plan-based truncation of returned history is exactly the kind of trait an agent must know before interpreting results. Missing are error behavior for invalid tickers or how the response is ordered/sized.

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?

Three short sentences, front-loaded with what the tool returns, then the coverage limits. Every sentence carries actionable information with zero filler.

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?

There is no output schema, so the description correctly enumerates the returned fields (open, high, low, close, volume) and the historical window. Ordering, timezone, pagination and empty-result behavior remain unspecified, which is a minor gap for a simple read tool.

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?

Schema coverage is 100% with examples for all four parameters, so the baseline is 3. The description adds the temporal bound of the data (May 2000 to today), which tells the agent what values of from/to are actually valid, but it does not clarify precedence or interaction between days and from/to.

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-resource: daily OHLCV for one NGX stock over a date range. The phrase 'one NGX stock' implicitly distinguishes it from index-oriented siblings such as get_index_history, but it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives clear entitlement context — Free keys get only the last 7 days, Starter+ get the full history back to May 2000 — which directly determines whether a call is worth making. It stops short of naming when to prefer another tool (e.g., an intraday or index variant), so no explicit exclusions are offered.

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