Skip to main content
Glama

save_sulvo_placement_plan

Save a placement revision. Input requires expectedVersion and payload.

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>",
      "input": "<input>"
    },
    "name": "save_sulvo_placement_plan"
  }
}

Input Schema

NameRequiredDescriptionDefault
inputYesA revision containing from 1 to 50 placements plus the consent/runtime attestations preflight requires.
workspaceIdYesActivation workspace identifier returned by the start or status tool.
outputFormatNomarkdown
idempotencyKeyNoOptional retry key. Reuse it when retrying the same mutation.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed5 schema fields changed
    • removedInput schema / additionalProperties
      Removed value: -false
    • changedInput schema / properties / input / additionalProperties
      Previous value: -trueNew value: +{}
    • addedInput schema / properties / input / properties / expectedVersion / maximum
      Added value: +9007199254740991
    • changedInput schema / properties / input / properties / payload / additionalProperties
      Previous value: -trueNew value: +{}
    • addedInput schema / properties / input / properties / payload / properties / placements / items / propertyNames
      Added value: +{
      +  "type": "string"
      +}
  2. First observed

TDQS

C2.9/5.0
Behavior2/5

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

The annotations already state readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly covered. The description adds little behavioral context beyond 'save': it does not explain optimistic version conflicts, idempotency behavior, why consent/runtime declarations must be true, or what happens to existing revisions.

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?

The description is two short sentences with the action front-loaded and no filler. The second sentence largely points back to schema requirements, but the overall structure is efficient.

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?

This is a complex nested mutation with no output schema and several workflow-sensitive siblings. The description omits prerequisite steps, conflict handling, idempotency guidance, and why the attestations matter, leaving it materially incomplete for correct invocation.

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 coverage is 75%, so the schema already documents most parameters. The description repeats that expectedVersion and payload are required, but does not add meaning such as expectedVersion being a concurrency token or explain workspaceId, idempotencyKey, outputFormat, or payload constraints.

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 states a specific verb and resource: 'Save a placement revision.' It is clear what the tool does, but it does not distinguish this tool from nearby siblings such as lock_sulvo_placement_revision or run_sulvo_activation_preflight.

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?

It gives only a bare input requirement ('expectedVersion and payload') and does not say when to use this mutation versus preflight, locking, review, or rollback tools. There are no explicit exclusions, prerequisites, or workflow guidance.

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.

Resources