Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_canned_service_labor

Remove a labor line item from a canned service template to update your service offerings without recreating the template.

Instructions

Remove a labor line item from 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": "remove_canned_service_labor"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemIdYesThe labor line item ID to remove
cannedServiceIdYesThe canned service ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A3.5/5.0
Behavior2/5

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

Without annotations, the description carries the full burden. It only says 'Remove' without disclosing side effects, permanence, permission requirements, or behavior when the item does not exist. This lack of detail leaves behavioral ambiguity for a destructive operation.

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, clear sentence with no unnecessary words or repetition. It is structurally efficient and immediately understandable.

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?

The description covers the basic intent but lacks contextual details such as whether the removal is permanent, whether it affects existing orders using the template, or what the expected return value is. For a destructive operation, this additional context would be valuable but is absent.

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 provides descriptions for both parameters (cannedServiceId and itemId), so the description does not add new meaning. It simply echoes the schema's own descriptions, resulting in no additional semantic value beyond what is already structured.

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 clearly states the action (remove) and the resource (a labor line item from a canned service template). It is specific enough to distinguish from sibling removal tools like remove_canned_service_fee or remove_canned_service_part.

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

Usage Guidelines3/5

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

The description implies usage by naming the exact resource, but it does not explicitly contrast with other removal tools or provide conditions for when to choose this tool over alternatives. No additional guidance such as prerequisites or when not to use it.

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

Deploy Server

Other Tools