Shopmonkey MCP Server

update_canned_service_subcontract

Update a subcontract line item on a canned service template to adjust its name, notes, quantity, description, cost, price, or tax status. Resolve mismatched subcontract details in Shopmonkey work orders.

Instructions

Update a subcontract line item on a canned service template.

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": {
      "cannedServiceId": "<cannedServiceId>",
      "itemId": "<itemId>"
    },
    "name": "update_canned_service_subcontract"
  }
}

Input Schema

Name	Required	Description
`name`	No	Updated subcontract name
`notes`	No	Additional notes
`itemId`	Yes	The subcontract line item ID to update
`quantity`	No	Updated quantity
`description`	No	Updated description
`unitCostCents`	No	Updated unit cost in integer cents
`unitPriceCents`	No	Updated unit price in integer cents
`cannedServiceId`	Yes	The canned service ID
`taxableValueType`	No	Taxable value type

Schema Changelog

Changes observed during successful MCP inspections.

Addedv1.1.1Sep 8, 2026

TDQS

C2.7/5.0

Behavior1/5

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

No annotations are provided, and the description does not disclose side effects, permissions, idempotency, required identifiers, or consequences of the update. It only states the basic intent.

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?

The description is a single concise sentence that directly communicates the tool's purpose without unnecessary detail.

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?

Given the nine parameters and no output schema or annotations, the one-sentence description leaves out important context such as which fields are optional, what the update does to existing values, and what the response contains.

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?

The schema already provides descriptions for all parameters, so the tool description adds no additional meaning. The schema descriptions are minimal but present; the description itself contributes nothing beyond the schema.

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 clearly states the action ('Update') and the resource ('a subcontract line item on a canned service template'). It is distinct from add/remove variants by operation type, though it does not explicitly name sibling tools.

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?

There is no explicit guidance on when to use this tool versus add/remove subcontract line items or other canned-service update tools. The verb 'Update' implies modifying an existing item, but that is not stated directly.

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

Deploy Server