bd-finance-mcp

List Sectors

list_sectors

Get the list of DSE sectors available for querying, such as Bank, Textile, and Pharmaceuticals, to start exploring sector performance and financial data.

Instructions

List the DSE sectors you can ask about, e.g. Bank, Textile, Pharmaceuticals.

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": "list_sectors"
  }
}

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Sep 8, 2026

TDQS

A3.9/5.0

Behavior4/5

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

There are no annotations, so the description carries the burden. For a zero-parameter list operation, 'List the DSE sectors...' transparently signals a non-mutating enumeration, and the examples clarify what kind of values will be returned; no hidden side effects are plausible for this tool.

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?

One short sentence with the key operation front-loaded and examples as supporting detail. There is no redundant text or repetition of the title beyond the essential verb.

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 tool with no parameters and an existing output schema, the description covers the core purpose and domain with examples. It could be more complete by pointing to downstream consumers such as sector_performance or noting ordering behavior, but those are not necessary for correct invocation.

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 has zero parameters and 100% schema coverage, so the baseline is 4. The description adds no parameter documentation (there are none), but the examples of sector names give useful operational value by showing the domain of returned values.

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 the action ('List') and the exact resource ('DSE sectors you can ask about'), with concrete examples (Bank, Textile, Pharmaceuticals) that make the domain unambiguous. It is clear, though it does not explicitly differentiate itself from sector_performance or other siblings.

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?

The phrase 'you can ask about' implies the tool is for discovering which sector names are valid inputs to other DSE queries, but no explicit when-to-use or alternative is given. An agent can infer the usage context but receives no direct routing guidance.

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

Deploy Server