Skip to main content
Glama

Kobo Terminal NGX

Fundamentals (all stocks)

get_fundamentals
Read-onlyIdempotent

Valuation, profitability, leverage and dividend metrics for 145 NGX stocks in one call: P/E, forward P/E, EPS, dividend per share, dividend yield, beta, ROE, ROA, P/B, debt/equity, margins, plus EV/EBITDA, PEG, F-score, RSI and analyst consensus. Plan: Starter+.

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_fundamentals"
  }
}

Input Schema

NameRequiredDescriptionDefault
symbolsNoComma-separated ticker filter. Example: GTCO,ZENITHBANK,MTNN

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered structurally. The description adds genuinely useful context beyond them: a fixed universe size (145 NGX stocks), a batch-in-one-call behavior, and a subscription-tier requirement. It says nothing about rate limits, freshness/latency of the data, or response shape.

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 front-loaded sentence covers scope, the metric list, and the plan requirement with no filler. The metric enumeration is long but each item is informative rather than redundant restatement of the title.

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 single-optional-parameter read tool with no output schema, the description supplies enough: what metrics come back, how many stocks are covered, and the plan gate. Only the interaction between the default (all stocks) and the symbols filter is left unstated.

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 single optional 'symbols' parameter is documented there with a comma-separated example, so the schema does the heavy lifting. The description never mentions the filter at all, so it adds no meaning beyond structured data; 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?

The description names a specific resource (fundamentals/valuation, profitability, leverage, dividend metrics) and enumerates the actual fields returned such as P/E, ROE, debt/equity and EV/EBITDA, so an agent can tell this is a fundamentals data endpoint rather than a price or disclosure endpoint. It lacks a leading verb and any explicit contrast with siblings like get_price_history or get_dividend_history, keeping it below 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no named alternative; the only routing signal is the implicit 'one call for all stocks' framing. The 'Plan: Starter+' note is a prerequisite that belongs in a guidance section, but it is the sole contextual hint and does not tell an agent when to prefer a different sibling.

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