Skip to main content
Glama

revise_proposal

Sends the revised version of a proposal after a member objects, using the draftId from the approved preview so the family sees what changed and voting restarts.

Instructions

Sends the next version of your own proposal after a member objected (status revising), exactly as preview_proposal prepared it with that proposalId: pass only its draftId, and only after the user said yes to this exact preview. Before the preview, read the objections with get_proposal and weigh the changed scenario again with the evaluate tools. The family sees what changed as was and now, and the votes start over. advisor.draft_stale (the numbers, the voters, the language or the proposal changed since the preview) or advisor.draft_not_found (expired after 30 minutes, sent already, or a new proposal's: send that with propose_to_family): prepare a new preview, show it, and ask for yes again. Without a draftId the answer is advisor.preview_required.

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": {
      "draftId": "<draftId>"
    },
    "name": "revise_proposal"
  }
}

Input Schema

NameRequiredDescriptionDefault
draftIdYesThe draftId preview_proposal answered for the card the user said yes to

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.8/5.0
Behavior5/5

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

Beyond readOnlyHint=false, it discloses side effects (votes restart, family sees was/now diffs), mutation prerequisites (exact user confirmation), and concrete error conditions including a 30-minute expiry. These are behavioral facts an agent could not infer from the annotation alone.

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?

Front-loaded with the action and the confirmation constraint, then prerequisites, then error handling in a logical order. The error-handling sentences are dense and slightly run-on, but each carries actionable information rather than filler.

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?

For a single-parameter mutation with no output schema, the definition covers preconditions, side effects, and every documented failure path, which is everything an agent needs to call it correctly. No output schema exists, so no return-value explanation is owed.

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% and there is only one parameter, so the baseline would be 3. The description nonetheless adds provenance semantics: pass only the draftId from the exact preview the user approved, and omitting it yields advisor.preview_required.

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 opens with a specific verb and resource: 'Sends the next version of your own proposal after a member objected (status revising)'. It scopes the tool to the user's own proposal in a specific status and ties it to preview_proposal output, making it clearly distinguishable from propose_to_family and preview_proposal.

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?

It states explicit preconditions: only after the user said yes to this exact preview, and before previewing, read objections with get_proposal and re-evaluate with the evaluate tools. It also routes failure cases to alternatives (advisor.draft_stale → new preview; draft not found/new proposal → propose_to_family).

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