Skip to main content
Glama
indian-option-mcp

indian-option-mcp

suggest_strategy

Generate options strategy suggestions tailored to your market outlook, risk tolerance, and available capital.

Instructions

Get AI-friendly strategy suggestions based on your market outlook, risk preference, and capital.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "outlook": "<outlook>"
    },
    "name": "suggest_strategy"
  }
}

Input Schema

NameRequiredDescriptionDefault
outlookYesYour market view
risk_levelNoMaximum acceptable risk level

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

C2.4/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full disclosure burden. It implies a read-only advisory call but never states that nothing is executed, whether results are ranked or filtered, how many suggestions return, or what happens when no strategy matches the given outlook and risk level.

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?

A single well-formed sentence with no filler and the core purpose front-loaded. It is efficient, though brevity comes at the cost of the missing usage guidance rather than because the content was well chosen.

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

Completeness2/5

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

With no output schema and no annotations, the description must explain what a "suggestion" actually is, and it does not. For a recommendation-style tool whose whole value is the returned content, leaving the response shape entirely unspecified is a real gap.

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

Parameters2/5

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

Schema coverage is 100%, so the baseline would be 3, but the description names "capital" as an input while the schema defines only outlook and risk_level. That fabricated parameter actively misleads an agent about what to supply, offsetting the value the sentence otherwise adds.

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

Purpose3/5

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

"Get AI-friendly strategy suggestions" states a verb and resource, so the general purpose is recoverable, but "AI-friendly" is vague and nothing separates it from siblings like build_strategy, custom_strategy, or list_strategies. An agent cannot tell from this text whether this tool returns pre-built recommendations or constructs a strategy.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use condition and no mention of alternatives. Given five sibling tools in the strategy family, the definition offers no routing logic, leaving the agent to guess whether to call this, build_strategy, or list_strategies first.

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