SKUit BOM Builder

Submit BOM Input

bom_submit_input

Submit user input for the current step of a BOM session. The message can be free text or one of the decision_chips returned by the previous step. Returns the updated BOM state, next step options, and decision chips. Continue calling this tool with the session_id until the session reaches the COMPLETE step. Going back or changing an earlier answer removes the affected lines from this in-progress draft; they can be chosen again, and no saved BOM is deleted.

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>",
      "message": "<message>"
    },
    "name": "bom_submit_input"
  }
}

Input Schema

Name	Required	Description	Default
`message`	Yes	User input — either free text or one of the decision_chips from the previous response
`session_id`	Yes	Session ID from bom_start_session

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 6, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, which the description does not contradict; it adds genuine context by clarifying that going back or changing an answer prunes lines from the in-progress draft only, and no saved BOM is deleted. It also names the return payload. Missing details on error/retry behavior keep it below 5.

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?

Four tight sentences, front-loaded with the action, then the loop contract, then the state-mutation caveat. No repetition or filler; every clause earns its place.

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?

With no output schema, the description compensates by naming the return values (updated BOM state, next step options, decision chips) and by explaining the termination condition and session continuity. An agent has everything needed to drive the session correctly.

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 100% and the schema already explains both message (free text or decision_chip) and session_id (from bom_start_session). The description restates the message semantics without adding format, length, or escaping guidance, so baseline 3 applies.

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?

States a specific verb ('Submit') plus resource ('user input for the current step of a BOM session'), and the sibling set (bom_start_session, bom_list_use_cases) makes clear this is the continuation/driving loop rather than session creation. Distinguishable without opening a schema.

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?

Gives explicit operating context: call repeatedly with the same session_id until the session reaches the COMPLETE step, and that the message may be free text or a decision_chip from the previous step. Lacks explicit exclusions relative to siblings, but the loop condition is actionable.

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

All SKUit BOM Builder tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?