Skip to main content
Glama

Kobo Terminal NGX

Bonds

get_bonds
Read-onlyIdempotent

Nigerian FGN bonds, Eurobonds, Sukuk and corporate bonds listed on the NGX: issuer, type, currency, coupon, maturity and latest quoted clean price (yield to maturity where published). 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": "get_bonds"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already declare this as a read-only, idempotent, open-world, non-destructive operation, so the safety burden is covered. The description adds genuinely useful context beyond that: the data is a snapshot ("latest quoted clean price"), yields are nullable ("where published"), and access requires the Free+ tier.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence front-loads the asset coverage and then the field list, followed by a short plan tag; nothing is padded. It is slightly run-on due to stacked commas and parentheses, but every clause carries 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?

With no input parameters and no output schema, the description's field enumeration is doing real work in telling the agent what a record contains. The remaining gap is scale and shape of the response (a flat list of all listed bonds vs. a paginated set), which is not stated but is also low-risk for a parameterless read.

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 no parameters and the schema correctly declares an empty object with additionalProperties false, so there is nothing to disambiguate. The description sensibly spends its words on the payload instead.

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 the exact resource and its coverage universe ("Nigerian FGN bonds, Eurobonds, Sukuk and corporate bonds listed on the NGX") and enumerates the returned fields, so an agent knows precisely what this returns. It does not explicitly contrast itself with siblings such as get_tbill_auctions or list_stocks, but the asset class is distinct enough that confusion is unlikely.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no statement of what this is an alternative to, and no exclusions. The only routing-adjacent information is "Plan: Free+", which describes entitlement rather than invocation 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