Skip to main content
Glama

Kobo Terminal NGX

Block-trade flow (market)

get_block_trade_flow
Read-onlyIdempotent

Net buying and selling in large trades (₦10 million and up) by stock over the last N days: where the big money is going. 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_block_trade_flow"
  }
}

Input Schema

NameRequiredDescriptionDefault
daysNoWindow in days, 1 to 90 (default 30). Example: 30

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

The annotations already declare read-only, non-destructive, idempotent, open-world behavior, so safety is covered. The description adds useful context with the ₦10 million threshold and the Free+ access tier. It does not describe output granularity, pagination, latency, or whether the data is delayed.

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?

The definition is short and front-loaded: it leads with the data being returned, then gives the threshold, then the plan note. Every phrase earns its place, and the informal 'where the big money is going' does not obscure the meaning.

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?

This is a simple read-only tool with one optional parameter, and the annotations cover its safety profile. The description supplies the key threshold and access tier, and it implies the returned shape as net buying and selling by stock. It is nearly complete, though it could mention any known data delay or return granularity.

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 description coverage is 100%, and the schema documents the days parameter with range, default, and example. The description only says 'over the last N days', which adds no meaning beyond the schema. The baseline of 3 is appropriate.

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 states a specific data resource: net buying and selling in large trades of ₦10 million or more, broken out by stock over the last N days. An agent can tell what the tool returns. It does not explicitly distinguish this from adjacent siblings such as insider dealings or price history.

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 explicit when-to-use or when-not-to-use guidance, and no alternative tools are named. The 'Plan: Free+' note hints at access tier but does not help the agent choose between this tool and related market data tools.

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