Skip to main content
Glama

participate

Enable agents to participate in multi-agent deliberation by submitting positions, publishing drafts, voting on a 5-point scale, and retrieving personal context such as clusters and allies. Supports signing and withdrawal.

Instructions

Participate in a deliberation. Actions:

  • submit_position: Submit your position (deliberation_id, agent_id, content; optional: model_family, group, conviction, reservation, on_behalf_of, interests, draft, metadata, signature)

  • publish_position: Publish a draft position (position_id)

  • vote: Vote on a position — value: -2=strongly_disagree, -1=disagree_with_caveats, 0=mixed, 1=agree_with_caveats, 2=strongly_agree (deliberation_id, agent_id, position_id, value; optional: qualifier, caveat, criterion_id, signature)

  • get_positions: Get all positions (deliberation_id; optional: round, exclude_agent_id, group, shuffle)

  • get_context: Get your personal context — cluster, allies, cruxes (deliberation_id, agent_id)

  • withdraw: Withdraw from a deliberation (deliberation_id, agent_id)

  • register_key: Register a base64 ed25519 public key for this agent (agent_id, public_key; optional: algo)

  • revoke_key: Revoke this agent's active signing key (agent_id)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
actionYes
deliberation_idNo
agent_idNo
contentNo
model_familyNo
groupNo
convictionNo
reservationNo
on_behalf_ofNo
interestsNo
draftNo
metadataNo
position_idNo
valueNo
qualifierNo
caveatNo
criterion_idNo
exclude_agent_idNo
roundNo
shuffleNo
signatureNo
public_keyNo
algoNo
Behavior3/5

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

The description discloses the behavior of each sub-action (e.g., 'Vote on a position — value: -2=strongly_disagree...') and lists relevant parameters. However, it does not cover side effects, permissions, failure modes, or constraints beyond the immediate actions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is verbose and lists actions in a dense paragraph. Bullet points or clearer separation of actions would improve readability. Every sentence adds some value, but the structure hinders quick scanning.

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?

Despite the complexity (23 params, 8 actions, no output schema), the description lacks information on return values, error handling, prerequisites (e.g., key registration), and interaction between actions. It provides enough to use basic actions but not comprehensive context.

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 partially compensates by grouping parameters per action (e.g., 'submit_position: ... optional: model_family, group...'). However, it does not fully explain all 23 parameters or their interdependencies, leaving ambiguity.

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 clearly defines the tool's purpose ('Participate in a deliberation') and breaks down eight distinct sub-actions with concise explanations. It effectively differentiates from sibling tools like 'decide' or 'deliberation' by focusing on participation actions.

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?

No explicit guidance on when to use this tool versus alternatives. The description lists sub-actions but does not provide decision criteria or context for choosing this tool over siblings like 'analyze' or 'coordinate'.

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/justinstimatze/gemot'

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