Skip to main content
Glama

Kobo Terminal NGX

Dividend history

get_dividend_history
Read-onlyIdempotent

Every dividend a company has paid: amount per share, ex-dividend date, record (qualification) date and payment date. 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_dividend_history"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoNumber of payments, or "all" (default)
symbolYesNGX ticker. Example: GTCO

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/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 safety is covered. The description adds one genuinely useful behavioral fact beyond them — the 'Free+' plan requirement, i.e. an access-tier gate. It says nothing about result ordering, pagination behavior, or how the `limit` interacts with the returned series.

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?

Two sentences, front-loaded with the substantive content and zero filler. The trailing 'Plan: Free+.' is terse and earns its place as an access constraint, though it reads as a bolted-on fragment rather than integrated prose.

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 simple two-parameter read tool with no output schema, the description does the important extra work of enumerating the returned fields, which the schema does not cover. Gaps are minor: no ordering of results, no handling of companies with no dividend history, and no resolution of the limit parameter's ambiguity.

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%, so both parameters are documented structurally, and the 3 baseline applies. The description adds no parameter-level meaning — it never mentions `limit` or explains the conflict between the schema's integer type and its 'or "all" (default)' note.

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 (dividends paid by a company) and enumerates exactly what is returned: amount per share, ex-dividend date, record/qualification date and payment date. 'Has paid' implicitly frames it as historical, which distinguishes it in spirit from get_dividend_calendar, but no sibling is named explicitly.

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 tool for past dividend payments on a ticker. There is no explicit when-to-use statement, no exclusion against get_dividend_calendar (upcoming dividends) or get_price_history, and no prerequisite guidance such as whether the symbol must be resolved first via lookup_identifiers.

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