Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

remove_canned_service_tire

Remove a tire line item from a canned service template by providing the canned service ID and tire item ID.

Instructions

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

Input Schema

NameRequiredDescriptionDefault
itemIdYesThe tire 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?

No annotations are provided, so the description carries the full burden. It states a removal action but does not disclose side effects, reversibility, idempotency, or error behavior. The minimal description leaves behavioral aspects transparent but insufficiently detailed.

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 with no unnecessary detail. It is well-structured and front-loaded with the primary action.

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 is adequate for a simple removal operation, but it lacks context about preconditions (e.g., whether the item must exist) or consequences (e.g., whether it permanently deletes or soft-deletes). Given the absence of an output schema, some assumptions remain unstated.

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 input schema already provides descriptions for both parameters (itemId and cannedServiceId), covering 100% of the fields. The description adds no extra semantic meaning beyond what the schema already provides, so the baseline 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: removing a tire line item from a canned service template. It specifies the resource (canned service) and the item type (tire), distinguishing it from other removal tools like remove_canned_service_part or remove_canned_service_fee.

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 is clear about what it does but does not explicitly mention when to use it over alternatives (e.g., update_canned_service_tire). It implies usage for removing tire items from canned templates, but lacks explicit guidance on selection criteria.

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