Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

add_canned_service_tire

Add a tire line item to an existing canned service template in Shopmonkey, specifying quantity, cost, and notes for accurate service records.

Instructions

Add a tire 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_tire"
  }
}

Input Schema

NameRequiredDescriptionDefault
nameNoTire name or description
notesNoAdditional notes
quantityNoNumber of tires
descriptionNoAdditional description
unitCostCentsNoUnit cost in integer cents
unitPriceCentsNoUnit price in integer cents
cannedServiceIdYesThe canned service ID to add the tire to
taxableValueTypeNoTaxable value type

Schema Changelog

Changes observed during successful MCP inspections.

  1. Addedv1.1.1

TDQS

A3.6/5.0
Behavior2/5

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

With no annotations, the description must convey behavioral impact. It says 'Add' indicating a write operation, but does not describe side effects, validation, or error conditions. This is minimal.

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?

Single concise sentence, front-loaded with the action.

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 simple add operation, the description is sufficient to understand the intent, though it doesn't explain what happens to existing line items. Acceptable.

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 covers all 8 parameters with descriptions. The tool description adds no additional meaning. Some descriptions like 'Additional description' are vague but exist. Baseline 3.

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 'Add', a specific resource 'tire line item', and target 'canned service template'. Clearly distinguishes from sibling tools like add_canned_service_fee or add_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?

Does not explicitly state when to use or not use this tool, though the sibling list implies it. It only says 'Add...' without mentioning alternatives or conditions.

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