Skip to main content
Glama
RevClamp MCP Server

RevClamp MCP Server

revclamp_reconcile_b2b_net_terms

Reconciles Shopify Plus B2B net-term invoices, deposits, credit notes, and rounding tolerances in EUR cents using double-entry accounting to verify wholesale payment balances.

Instructions

Reconciles Shopify Plus B2B Net-15/30/60 (and custom 1..180-day) wholesale invoices, upfront deposits, credit notes, and rounding tolerances using integer EUR-cent double-entry accounting.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "revclamp_reconcile_b2b_net_terms"
  }
}

Input Schema

NameRequiredDescriptionDefault
demoNo
orderIdNo
toleranceCentsNo
creditNoteCentsNo
orderTotalCentsNo
paidAmountCentsNo
totalOrderCentsNo
creditNotesCentsNo
paymentTermsDaysNo
invoiceIssuedAtSecNo
requiredDepositCentsNo
requiredDepositPercentNo
daysElapsedSinceInvoiceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changedv1.20.32
    • addedInput schema / properties / invoiceIssuedAtSec
      Added value: +{
      +  "minimum": 1,
      +  "type": "integer"
      +}
    • removedInput schema / properties / paymentTermsDays / enum
      Removed value: -[
      -  15,
      -  30,
      -  60
      -]
    • addedInput schema / properties / paymentTermsDays / maximum
      Added value: +180
    • addedInput schema / properties / paymentTermsDays / minimum
      Added value: +1
  2. Addedv1.20.29
  3. Removedv1.0.1
  4. First observedv1.0.0

TDQS

C2.6/5.0
Behavior2/5

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

No annotations are supplied, so the description carries the full burden. It hints at the method ('integer EUR-cent double-entry accounting') and that tolerances are handled, but it never says whether the tool writes or persists anything, whether it is idempotent, what the response contains, what happens when amounts don't reconcile, or how the 1..180-day terms affect output.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single dense sentence with the verb front-loaded and no filler, which is good. However, it packs qualifiers like 'Net-15/30/60 (and custom 1..180-day)' and 'integer EUR-cent double-entry' while omitting the operational essentials, so the brevity reflects underspecification rather than economy.

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

Completeness2/5

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

This is a 13-parameter financial reconciliation tool with zero annotations, no output schema, and notably zero required parameters, so the agent gets no signal about which inputs are mandatory versus optional. The description does not come close to covering what an agent needs to call it correctly or to interpret a result.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% across 13 parameters, and the schema contains near-duplicate names (orderTotalCents vs totalOrderCents, creditNoteCents vs creditNotesCents, plus paidAmountCents/requiredDepositCents/requiredDepositPercent) that urgently need disambiguation. The description only loosely gestures at these concepts ('credit notes', 'upfront deposits', payment terms) without mapping meaning to any named parameter, so it does not compensate for the coverage gap.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('Reconciles') plus a well-defined resource set: B2B wholesale invoices, upfront deposits, credit notes, and rounding tolerances. The domain is unmistakable and quite distinct from the siblings (audit, ROI, VAT, webhook tools), but the description never explicitly differentiates itself or names an alternative, so it stops short of a 5.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, no prerequisites (e.g., data must come from Shopify Plus B2B), and no reference to any sibling tool or workflow step. An agent must infer the invocation context entirely from the one-sentence purpose.

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