Skip to main content
Glama

get_stock_debate

Conducts a 3-round AI debate on a stock symbol, where agents read each other's arguments and may revise verdicts. Returns final consensus and influence graph.

Instructions

3-round sequential debate: AI agents read each other's arguments and rebut.

Unlike get_stock_brief (parallel analysis), this runs a live debate: Round 1 - Each agent analyses independently Round 2 - Each agent reads all other Round 1 verdicts and can change mind Round 3 - Final lock-in with closing statement

Watch for "minds_changed" - when agents flip verdict mid-debate, it signals a complex setup worth closer attention.

Also returns "debate_edges" - who influenced whom - consumable by the AgentBattle canvas visualisation.

Args: symbol: NSE stock symbol (e.g. RELIANCE, TCS, HDFCBANK)

Returns JSON with: - rounds: {round1, round2, round3} - full transcript - debate_edges: [{from, to, type, text}] - influence graph - minds_changed: how many agents revised their verdict - final_consensus: {signal, strength, votes, note}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
symbolYes

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

Describes the full 3-round process, agent interactions, and all return fields (rounds, debate_edges, minds_changed, final_consensus). No annotations, but description carries the burden well, though it omits prerequisites or rate limits.

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?

Well-structured with bullet points and section headers. Front-loaded with purpose. Every sentence adds value, no fluff. Appropriate length for the complexity.

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?

Covers all major aspects: rounds, influence graph, consensus. Mentions visualization use case. Lacks error details or preconditions, but for a debate tool this is sufficient.

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?

The only parameter 'symbol' has 0% schema description coverage, but the description adds examples and clarifies it's an NSE symbol. Adds some value beyond the schema, but not extensive detail.

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?

Clearly states '3-round sequential debate' and distinguishes from sibling get_stock_brief. Uses specific verb 'runs a live debate' and describes resource (stock symbol) with detailed round mechanics.

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

Usage Guidelines4/5

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

Explicitly contrasts with get_stock_brief (parallel analysis) and advises watching for minds_changed to identify complex setups. Could be more explicit about when not to use, but provides clear context.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/finstacklabs/finstack-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server