Skip to main content
Glama
indian-option-mcp

indian-option-mcp

list_strategies

Lists all pre-built options strategies for Indian markets and filters them by category such as BULLISH, BEARISH, NEUTRAL, or VOLATILITY to find a matching setup.

Instructions

List all available pre-built options strategies, optionally filtered by category.

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

Input Schema

NameRequiredDescriptionDefault
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. The verb 'list' makes it reasonably clear that this is a non-mutating enumeration tool, but the description does not say whether results are static or user-specific, whether pagination or rate limits exist, or what a returned strategy record contains. This is adequate but thin, given that there are zero annotations.

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?

The description is a single well-formed sentence, with the core action front-loaded and the optional filter stated second. There is no redundant or filler wording.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

This is a simple one-optional-parameter read tool with no output schema, so the description does not need to explain return values. Still, it never indicates what a 'pre-built strategy' consists of, or how its result connects to build_strategy or calculate_payoff, which would help an agent chain calls.

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?

With 0% schema description coverage, the description must compensate for the single category parameter. It adds that the filter is optional and is a filtering dimension, and the enum values (BULLISH, BEARISH, NEUTRAL, VOLATILITY) are self-explanatory, so meaning is largely conveyed. It does not say whether the filter matches strategy direction only or includes a volatility bucket, or what happens when the category is invalid.

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 states a specific verb and resource ('List all available pre-built options strategies'), and the word 'pre-built' implicitly separates it from the sibling tools build_strategy and custom_strategy. It does not name any alternative explicitly, but an agent can tell this is a catalog-listing tool rather than a builder.

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 'optionally filtered by category' implies when the filter is applicable, which is useful minimal guidance. However, the description never says when to call this tool rather than suggest_strategy or build_strategy, and it does not say what the categories mean or what to do if no category is supplied.

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