Skip to main content
Glama

Challenge my position

challenge

Submit a position to multiple AI debaters, respond to their questions, and iterate until the debate is settled, then synthesize a final answer.

Instructions

Present your position to the saved debaters and run a discussion before you answer. When the user has activated kontra mode (e.g. said "kontra mode on"), ALWAYS run this loop before answering substantive questions. The loop: (1) call with your position; (2) answer the debaters' questions directly, respond to their specific points, ask questions back where their objections are ambiguous, then call again with the FULL transcript (debater replies under their names, your own turns as speaker 'host'); (3) keep going for as many rounds as the debate needs. The 'status' field is 'settled' once every debater has nothing new to add (or the round cap is hit), or 'error' if every debater failed; never synthesize while it is 'continue'. If the result is an onboarding message about a missing API key, relay it to the user and stop; do not retry until they confirm the key is set. To change the debaters or round limit, use configure_debate (it saves). Follow the 'instruction' field in the result for how to format your final reply.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
topicYesthe user's question, restated
positionYesthe host's current argument or answer
transcriptNoprior rounds in order; debater replies under their names, your turns as 'host'
Behavior5/5

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

No annotations provided, so description carries full burden. It details the loop steps, status field meanings ('settled', 'error', 'continue'), error handling for missing API key, and the 'instruction' field. No contradictions found.

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?

The description is dense but well-structured, with the loop steps clearly enumerated. It is slightly long but every sentence adds value. Front-loaded with purpose and usage condition.

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

Completeness5/5

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

Given no output schema, the description explains return value fields (status, instruction) and covers edge cases like missing API key and round caps. It is fully comprehensive for the tool's complexity.

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?

Schema covers 100% of parameters with descriptions. The description adds context: 'topic' is the user's question restated, 'position' is the host's argument, 'transcript' includes prior rounds with speaker names. This adds value beyond schema.

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?

The description clearly states the tool's purpose: 'Present your position to the saved debaters and run a discussion before you answer.' It distinguishes from sibling tools by specifying that configure_debate is used for changing debaters or round limits.

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

Usage Guidelines5/5

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

Explicitly states when to use: 'When the user has activated kontra mode ... ALWAYS run this loop before answering substantive questions.' It also provides alternatives (configure_debate for configuration) and stopping conditions.

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/a1ex-bb/kontra'

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