Skip to main content
Glama
Sign In
cse-mcp

cse-mcp

by lxnid
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Sector indices

get_sector_indices
Read-onlyIdempotent

Fetch all Colombo Stock Exchange sector indices with today's values, changes, and activity, ordered by performance and including IDs for historical lookups.

Instructions

All CSE sector indices (S&P/CSE industry groups such as Banks, Energy, Capital Goods) with today's value, change and activity, best performers first. The index_id can be passed to get_index_history.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely new behavior beyond them: the result set is the full sector list, entries are sorted by performance, and the payload carries value/change/activity rather than raw quotes. It omits refresh cadence and exchange coverage, which keeps it short of a 5.

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 sentences, front-loaded with what is returned and how it is ordered, then the chaining hint. No filler, no 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?

Because an output schema exists, return-field documentation is not required, and the description covers scope, contents and ordering. What is left out — data freshness and which exchange the CSE indices cover — is minor for a zero-parameter read tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes no parameters, so the baseline is 4. The description goes slightly further by explaining the meaning of the index_id field present in the response and where that value can be reused, which aids downstream chaining even though there is nothing to disambiguate on input.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a concrete resource (all CSE sector indices, naming S&P/CSE industry groups like Banks, Energy, Capital Goods) plus what each entry contains (today's value, change, activity) and the ordering (best performers first). An agent can tell this apart from get_market_overview or get_index_history without consulting the schema.

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 implied as a browse-the-sectors call, and it gives one useful routing hint: the returned index_id can be passed to get_index_history. It never states when to prefer this over siblings such as get_market_overview or get_market_daily_summary, and there are no prerequisites or exclusions spelled out.

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