Skip to main content
Glama
Sign In
cse-mcp

cse-mcp

by lxnid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Announcements

get_announcements
Read-onlyIdempotent

Retrieve and filter Colombo Stock Exchange announcements by category, company, ticker, or keyword to find corporate, financial, and regulatory notices.

Instructions

Latest CSE announcements, newest first.

- corporate: dividends, rights issues, AGMs, board changes, XD/payment dates
- financial: quarterly/annual financial statements (with PDF links)
- non_compliance, new_listings, buy_in_board: regulatory notices
- circulars, directives: CSE/SEC rule circulars and directives

`query` filters by company name, ticker or text (e.g. "JKH", "dividend").

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNo
categoryNocorporate

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the bar is lower. The description adds real context beyond them: default-newest ordering, what each category contains (PDF links on financials, XD/payment dates on corporate), and how query matching works.

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?

Front-loaded one-line purpose followed by a tight category taxonomy and a single sentence on query. Well structured with no filler, though 'CSE' is left unexpanded for a non-local agent.

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?

An output schema exists, so return values need not be described. Combined with clear category and query semantics, the definition is nearly complete for a simple list tool; the only gap is undocumented limit behavior.

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 0%, so the description must carry the burden. It fully explains the category enum values and query matching (company name, ticker, free text, with an example), but never mentions the limit parameter or its default of 15, leaving one of three params opaque.

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?

States a specific verb and resource ('Latest CSE announcements, newest first') and enumerates the categories it covers. It never explicitly contrasts itself with the market-data siblings, but the resource domain is unmistakable.

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: 'Latest ... newest first' plus category bullets suggest when each category is relevant, and the query example hints at lookup patterns. There is no explicit when-to-use versus alternative guidance for the sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools