Skip to main content
Glama

Kobo Terminal NGX

Dividend calendar

get_dividend_calendar
Read-onlyIdempotent

Dividends across the whole market by ex-dividend date. Use upcoming=true for what is coming next. 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_dividend_calendar"
  }
}

Input Schema

NameRequiredDescriptionDefault
toNoLatest ex-date, YYYY-MM-DD
fromNoEarliest ex-date, YYYY-MM-DD (default 90 days ago)
limitNoDefault 200, max 500
symbolNoFilter by ticker
upcomingNoOnly ex-dates from today forward, soonest first. Example: true

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 this as a read-only, idempotent, non-destructive open-world query, so the safety profile is covered. The description adds a plan-gating constraint ("Plan: Free+"), which is genuinely useful context not in the structured fields, but it is terse and does not say what happens on an ineligible plan (error vs. empty result).

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?

Two short sentences plus a plan fragment carry scope, ordering, the key flag, and tier availability with zero waste, and the core scope statement is front-loaded. Nothing is padded or repeated from the schema.

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 zero required parameters, a fully documented schema, and annotations covering the safety profile, the definition is close to complete for this tool's complexity. The remaining gap is that it never clarifies the difference from the sibling dividend-history tool or the result ordering when `upcoming` is false.

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%, with every parameter documented including defaults (90 days ago, limit 200/max 500) and an example for `upcoming`. The description only restates the `upcoming` usage already present in the schema, adding no new semantics, so the 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 (dividends) and its scope ("across the whole market") plus the ordering key (ex-dividend date), so an agent knows exactly what comes back. It does not distinguish itself from the sibling get_dividend_history, which is the one most likely to be confused with it.

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?

One concrete usage hint is given: use `upcoming=true` for what is coming next. There is no guidance on when to prefer this over get_dividend_history, and no statement of when not to use it; the routing decision is left to inference from the tool name.

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