Skip to main content
Glama

Kobo Terminal NGX

All stocks (daily price list)

list_stocks
Read-onlyIdempotent

Every listed NGX equity in one call: price, previous close, open/high/low, change, 7-day change, volume, value, trades, market cap, shares outstanding and sector. 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_stocks"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/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 usefully adds the exact fields returned (price, change, market cap, sector, etc.) and the 'Free+' plan requirement, which are not in any structured field. It stops short of noting data freshness or response size.

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?

One sentence, zero waste, with the resource and scope front-loaded before the field enumeration and the plan note. Every element (fields, plan tier) carries information an agent cannot get from the schema or annotations.

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 zero-parameter list tool with no output schema, the description supplies the return payload and tier requirement, which is what an agent needs to choose and call it. Minor gaps remain around freshness and whether the list is paginated or truncated.

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 no parameter semantics to document and the baseline of 4 applies. The description correctly makes no parameter claims and instead spends its words on payload content.

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 resource and scope: 'Every listed NGX equity in one call.' The exchange qualifier (NGX) plus 'equity' implicitly separates it from siblings like list_nasd_stocks, list_etfs, and list_indices, though no sibling is named directly.

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?

'In one call' hints this is the bulk/whole-market endpoint rather than a filtered lookup, and 'Free+' signals tier availability. However, there is no explicit statement of when to prefer this over get_fundamentals, get_price_history, or the NASD list.

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