Skip to main content
Glama

set_proposal_status

Approve, reject, or reset a saved proposal. Use this in external MCP clients when the user approves or rejects a proposal in chat, so the Sequencer edit state stays in sync without relying on a Spark-only UI modal.

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": {
      "workspaceId": "<workspaceId>",
      "editId": "<editId>",
      "status": "<status>"
    },
    "name": "set_proposal_status"
  }
}

Input Schema

NameRequiredDescriptionDefault
noteNoOptional short note about why the proposal was approved, rejected, or reset
editIdYesThe edit ID
statusYesNew proposal status
proposalIdNoSpecific proposal ID. If omitted, the active proposal for the edit is used.
workspaceIdYesThe workspace ID
approvalScopeNoUse plan_images_budget only after explicit approval of the plan, displayed starting images and quoted total budget.plan
expectedVersionNoReviewed proposal version, required for combined approval.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / approvalScope
      Added value: +{
      +  "default": "plan",
      +  "description": "Use plan_images_budget only after explicit approval of the plan, displayed starting images and quoted total budget.",
      +  "enum": [
      +    "plan",
      +    "budget",
      +    "plan_images_budget"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / expectedVersion
      Added value: +{
      +  "description": "Reviewed proposal version, required for combined approval.",
      +  "exclusiveMinimum": 0,
      +  "type": "integer"
      +}
  2. First observed

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full burden. It discloses the key side effect — synchronizing Sequencer edit state — but says nothing about reversibility, permission requirements, idempotency, or what combined approval triggers, which are significant gaps for a state-mutating tool.

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?

Two sentences, front-loaded with the action and followed by the situational rationale. Nothing is redundant, though the second sentence is dense and the Spark-modal reference is more context than instruction.

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

Completeness3/5

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

With seven parameters, two enums, a conditional requirement (expectedVersion for combined approval), and no output schema, the description covers purpose and timing but not outcomes. An agent still cannot tell what a call returns or what downstream effects approval of a plan/budget scope produces.

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%, so all seven parameters, both enums, and the expectedVersion constraint are already documented in the schema. The description adds no parameter-level meaning beyond that, which is the expected baseline.

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 opens with a specific verb set and resource: 'Approve, reject, or reset a saved proposal,' which maps directly onto the status enum values. It is distinguishable from generic update tools, though it does not explicitly contrast itself with siblings like set_asset_approval_status or update_proposal.

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

Usage Guidelines4/5

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

It names a clear usage context ('in external MCP clients when the user approves or rejects a proposal in chat') and a reason (keeping Sequencer edit state in sync). There is no explicit when-not guidance or named alternative, and the 'reset' case is not given a similar scenario.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.