macp-mcp

Official

Overview Schema Source Related Servers Discussions Admin

vote

Cast an approval, rejection, or abstention on a proposal in a governed MACP session, limited to one response per agent per proposal.

Instructions

Cast this agent's vote on a proposal. One vote per agent per proposal.

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": {
      "session_id": "<session_id>",
      "proposal_id": "<proposal_id>",
      "vote": "<vote>"
    },
    "name": "vote"
  }
}

Input Schema

Name	Required	Description
`vote`	Yes	Your vote.
`reason`	No	Why.
`session_id`	Yes	The MACP session id (from start_session).
`proposal_id`	Yes	Short identifier for the proposal, unique within the session.

Output Schema

Name	Required	Description	Default
`ok`	Yes
`vote`	Yes
`sender`	Yes
`duplicate`	Yes
`message_id`	Yes
`session_id`	Yes
`proposal_id`	Yes
`session_state`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.2.0Oct 27, 2026

TDQS

A3.6/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, so the safety profile is known. The description adds one genuinely useful behavioral fact beyond the structured data: the one-vote-per-agent-per-proposal constraint. It does not say whether a vote can be changed/revoked, what happens on a duplicate attempt, or whether voting is final.

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?

Two short sentences, zero filler, with the core action front-loaded and the constraint immediately following. Nothing to trim.

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?

With an output schema, full schema coverage and safety annotations present, most remaining burden is lifted. The only real gap is the lifecycle question: whether a cast vote is final or replaceable, which matters for a per-agent-unique action in a voting workflow.

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?

Schema description coverage is 100% and the vote enum is self-documenting, so the schema carries the parameter burden. The description adds no extra meaning about session_id scoping or how `reason` is used (recorded? surfaced to other agents?), leaving the baseline 3 appropriate.

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?

States a specific verb and resource ("Cast this agent's vote on a proposal"), which an agent can distinguish from propose/commit/evaluate by the action word alone. It does not explicitly contrast with the closest sibling (commit), so it stops short of full sibling differentiation.

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

Usage Guidelines3/5

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

"on a proposal" implies this is the step that acts on output of propose, which weakly signals usage. There is no statement of when to vote versus commit or evaluate, no prerequisites (e.g. requiring an open session in a voting state), and no exclusions.

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

Deploy Server