Skip to main content
Glama

Kobo Terminal NGX

Market summary

get_market_summary
Read-onlyIdempotent

NGX All-Share Index level and daily change, market capitalisation, volume, value, deals and breadth (advancers, decliners, unchanged). 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_market_summary"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/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 needs no restating. The description adds one genuine behavioral fact not in structured fields — the 'Plan: Free+' access tier — plus the payload contents. However, it says nothing about data freshness (realtime vs end-of-day) or whether a stale/previous close is returned outside trading hours, which matters for market data.

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?

One sentence, front-loaded with the headline metric (index level and daily change) before the secondary fields. The enumerated field list is dense but each item conveys return-value content, so nothing is wasted. A short note on freshness would be worth the extra line.

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, the description carries the full burden of describing the return payload, and it does so field by field. No parameters exist to document. The only omission is temporal behavior (snapshot timing/freshness), which an agent would want before trusting the figures.

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 the schema imposes no semantic burden and the baseline is 4. The description correctly adds no parameter chatter, which is appropriate for a parameterless call.

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?

Names the specific resource (NGX All-Share Index) and enumerates exactly what the response carries: level, daily change, market cap, volume, value, deals, and breadth components. An agent knows precisely what this returns. It does not explicitly distinguish itself from the adjacent get_market_status or get_index, so it stops short of a 5.

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 top-level market snapshot tool and that 'NGX' scopes it to the Nigerian exchange. There is no explicit when-to-use, no exclusions, and no named alternative (e.g. get_market_status or get_index) for a narrower or different view.

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