Skip to main content
Glama

Kobo Terminal NGX

All ETFs

list_etfs
Read-onlyIdempotent

Every NGX exchange-traded fund with ISIN, issuer, previous close, open/high/low, change, trades, volume and value. 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_etfs"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds useful context the annotations do not: the exact payload fields and the 'Free+' plan requirement. It says nothing about result size, pagination, or ordering despite returning an entire catalog in one call.

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 front-loaded sentence with no filler; the resource comes first and the field list follows. The 'Plan: Free+' clause is short and carries access information an agent would otherwise have to learn from an error.

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 and no parameters, the description carries the burden of describing results and does so by enumerating the fields. It is slightly incomplete on volume or ordering of a full-catalog response, but nothing essential for correct invocation 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 no parameter semantics to explain; the baseline of 4 applies. The description keeps the returned-field list, which is the only structured information the empty schema cannot provide.

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 NGX exchange-traded fund', and enumerates the exact fields returned (ISIN, issuer, previous close, OHLC, change, trades, volume, value). It does not explicitly contrast with the sibling get_etf for single-fund lookups, so differentiation is left implicit.

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?

'Every NGX exchange-traded fund' implies a full-catalog listing use case, and 'Plan: Free+' signals an access-tier prerequisite. Beyond that there is no explicit when-to-use or when-not-to-use guidance, and no pointer to get_etf for single-fund detail.

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