Skip to main content
Glama

moa_submit_turn

Submit an agent's debate turn with content, validate turn order, and advance to the next speaker. Optionally cast a signoff vote for early unanimous close.

Instructions

Submit this agent's turn content. Validates turn order ({error:"not_your_turn"} otherwise), advances to the next speaker. Pass signoff:true to cast an early-close (unanimous signoff) vote; when every agent has signed off the debate closes early ({debate_complete:true, early:true, reason:"unanimous_signoff"}). Any normal (non-signoff) submission counts as dissent and resets accumulated signoffs.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
contentYesThe agent's debate contribution for this turn (the signoff statement when signoff is true)
signoffNoTrue to cast an early-close (unanimous signoff) vote instead of a normal turn; content carries the signoff statement. A normal (non-signoff) submission is a dissent that clears all accumulated signoffs.
task_idYesMOA task id
agent_idYesDebate agent id (must be in preset agents)
Behavior5/5

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

With no annotations, the description fully bears the burden. It discloses turn order validation, next-speaker advancement, signoff mechanism, dissent behavior, and early-close conditions. No contradictions or omissions.

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?

Four sentences, front-loaded with the main purpose. Every sentence adds essential information. No redundancy or unnecessary detail.

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?

Despite no output schema, the description fully covers behavior, error cases, and completion conditions. It explains both normal and signoff workflows completely, enabling correct tool invocation.

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 coverage is 100%, baseline 3. The description adds extra context: explains content as debate contribution or signoff statement, signoff's effect on early-close, and the role of task_id/agent_id. This goes beyond the schema descriptions.

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 submits the agent's turn content, validates turn order, and advances the speaker. It distinguishes itself from sibling tools like moa_wait_turn and moa_complete by describing its specific role in the debate flow.

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 (to submit turn content) and what happens if used out of turn (error). Explains the signoff option and its implications, implying when not to use signoff (normal submission as dissent). Provides clear context for selection.

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/Yorha9e/moamcp'

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