Skip to main content
Glama
Sign In
Shopmonkey MCP Server

Shopmonkey MCP Server

by AbbottDevelopments
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

create_payment

Record a new payment for a work order in Shopmonkey by specifying order ID, amount in cents, payment method, and optional notes.

Instructions

Record a new payment in Shopmonkey.

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": {
      "orderId": "<orderId>",
      "amountCents": "<amountCents>"
    },
    "name": "create_payment"
  }
}

Input Schema

NameRequiredDescriptionDefault
notesNoAdditional notes about the payment
methodNoPayment method (e.g., cash, credit_card, check)
orderIdYesWork order ID to apply the payment to
amountCentsYesPayment amount in integer cents. Example: $150.50 = 15050. NEVER send a decimal value.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changedv1.1.1
    • removedInput schema / properties / amount
      Removed value: -{
-  "description": "Payment amount in dollars",
-  "type": "number"
-}
    • addedInput schema / properties / amountCents
      Added value: +{
+  "description": "Payment amount in integer cents. Example: $150.50 = 15050. NEVER send a decimal value.",
+  "type": "number"
+}
    • changedInput schema / required
      Previous value: -[
-  "orderId",
-  "amount"
-]New value: +[
+  "orderId",
+  "amountCents"
+]
  2. First observedv1.0.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It states that a new payment is recorded, implying a write operation, but does not disclose side effects (e.g., updates to order balance), validation rules, or idempotency. Basic behavior is clear, but deeper consequences are not covered.

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 front-loads the action ('Record') and the resource ('payment'). It contains no fluff and is efficiently structured.

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 tool is a simple create operation, and the description gives the essential purpose. However, the absence of an output schema and annotations leaves the return value and error behavior unspecified, which may require the agent to make assumptions. It is adequate but not fully complete.

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 description coverage is 100%: all four parameters (orderId, amountCents, method, notes) have descriptions. The tool description adds no additional semantic value beyond the schema, so the baseline score of 3 applies.

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 'Record a new payment in Shopmonkey' clearly specifies the action (recording/creating) and the resource (payment). It is distinct from sibling tools like get_payment and list_payments, making the purpose unambiguous.

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 implicitly indicates this tool is for creating new payments, and sibling tools for retrieving payments exist, but it does not explicitly state when to use this tool versus alternatives. The usage is implied rather than explicitly stated.

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