Skip to main content
Glama

Kobo Terminal NGX

Single ETF

get_etf
Read-onlyIdempotent

One ETF by symbol. Common aliases are resolved to the canonical NGX symbol. 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": {
      "symbol": "<symbol>"
    },
    "name": "get_etf"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolYesETF symbol or alias. Example: STANBICETF30

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 two non-obvious behaviors: alias strings are resolved to the canonical NGX symbol, and access is gated by a "Free+" plan tier.

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, zero filler, with the core purpose front-loaded before the alias and plan caveats. Nothing is repeated from the schema and nothing could be cut without losing information.

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 one-parameter read tool with full schema coverage and rich annotations, this is nearly complete: purpose, identifier resolution, and access tier are all stated. Gaps are minor — no indication of what an unknown alias yields, and the cryptic "Plan: Free+" wording could be spelled out.

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?

Schema coverage is 100% and the schema already labels the field as "ETF symbol or alias" with an example. The description's alias-resolution note adds slight context but no new syntax, format, or validation detail beyond what the schema supplies, so baseline 3 applies.

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?

"One ETF by symbol" is a specific verb+resource pair that clearly separates this single-record fetch from the batch sibling list_etfs. It does not name the sibling explicitly, but the singular/plural split is self-evident.

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?

Usage is only implied: an agent can infer this is the lookup path once a symbol is known, versus list_etfs for discovery. There is no explicit "use this when..." statement or stated prerequisite such as knowing the symbol beforehand.

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