market_summaryRetrieve a concise Dhaka Stock Exchange market snapshot with DSEX and DS30 index changes, session totals, and DSES figures from the 30-day market information table.
Latest market snapshot: DSEX/DS30 indices + changes, session totals, and DSES from the 30-day market information table.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the behavioral disclosure burden. It does communicate that the result is a 'latest' snapshot sourced from a '30-day market information table,' implying a read-only, current view. However, it does not explicitly state that it has no side effects, whether data is cached, or how often it refreshes.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, focused sentence with no wasted words. It front-loads the core concept ('Latest market snapshot') and then lists the specific data elements, making it easy for an agent to parse quickly.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
For a zero-parameter tool with an output schema present, the description is nearly complete: it names all returned content areas and the data source. The only notable gap is the absence of routing context versus similar market tools, but this does not prevent correct invocation.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The tool has zero parameters, so the schema fully defines invocation requirements and the description need not explain parameter details. The baseline of 4 applies because there is nothing meaningful to add about parameter semantics.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly identifies the resource as a latest market snapshot and enumerates its contents: DSEX/DS30 indices, changes, session totals, and DSES. It is not phrased with a strong action verb, but the noun-phrase 'Latest market snapshot' makes the retrieval behavior clear enough and helps distinguish it from historical or sector-specific siblings.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description gives no explicit guidance about when to choose this tool over alternatives such as market_status or get_index_history. The reader can infer that it is for a current market overview, but there are no stated exclusions, conditions, or sibling routing hints.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.