Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_canned_service_labor

Add a labor line item to an existing canned service template in Shopmonkey.

Instructions

Add a labor line item to an existing 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>"
    },
    "name": "add_canned_service_labor"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoLabor name
noteNoAdditional notes
hoursNoLabor hours (e.g. 2.5)
taxableNoWhether this labor line is taxable
rateCentsNoBilled labor rate per hour, in integer cents
costRateCentsNoInternal cost rate per hour, in integer cents
cannedServiceIdYesThe canned service ID to add labor to

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A3.8/5.0
Behavior3/5

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

With no annotations provided, the description carries the transparency burden. It accurately indicates a create/add operation but does not disclose side effects, failure behavior, or whether adding is idempotent.

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 wording or redundancy.

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

Completeness4/5

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

For a straightforward additive operation with fully described parameters and no output schema, the description is largely complete. It could be slightly richer about expected behavior, but the current text plus schema gives adequate context.

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 describes all parameters, and the description adds no meaningful semantic detail beyond what is already in the input schema, so the baseline score of 3 is appropriate.

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 ('Add'), the object ('labor line item'), and the target ('existing canned service template'), which distinguishes it from related tools like add_canned_service_fee or update_canned_service_labor.

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 the use case by naming the operation, but it does not explicitly contrast it with alternatives such as update_canned_service_labor or remove_canned_service_labor, leaving the agent to infer when this tool should be preferred.

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