Skip to main content
Glama

FavCRM

by io.favcrm
OverviewDiscussionsAdmin

preview_customer_import

Preview a bulk customer import (max 2000 rows). Matches existing accounts by phone/email and shows create vs update actions plus points/stamps/credit deltas. Use commit_customer_import with the returned sessionId to apply.

Input Schema

NameRequiredDescriptionDefault
rowsYes
filenameNoOriginal filename for audit

Output Schema

NameRequiredDescriptionDefault
dataYesTool result payload — shape varies per tool, see the tool description
summaryYesOne-line human-readable summary of the action
renderTypeYesUI rendering hint for the result

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / rows / items / properties / lifeStage / anyOf
      Previous value: -[
-  {
-    "enum": [
-      "lead",
-      "active",
-      "churned",
-      "vip"
-    ],
-    "type": "string"
-  },
-  {
-    "type": "null"
-  }
-]New value: +[
+  {
+    "enum": [
+      "lead",
+      "active",
+      "churned",
+      "vip",
+      "prospect"
+    ],
+    "type": "string"
+  },
+  {
+    "type": "null"
+  }
+]
  2. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, but the description adds real substance: the 2000-row cap, the phone/email matching key, and the delta fields the preview returns. It stops short of clarifying that the non-read-only behavior is session creation (the preview does not mutate accounts), which is the one ambiguity an agent might trip on.

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?

Three dense sentences, zero filler, front-loaded with the action and limit, then behavior, then the follow-up tool. Every clause carries operational information.

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?

An output schema exists, so return shape need not be spelled out, and the description still summarizes the key return contents. The workflow (preview then commit) is complete, though session lifetime or expiry is not mentioned.

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

Parameters4/5

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

Schema coverage is only 50%, but the description compensates by identifying the semantically load-bearing fields: phone/email as the account-matching keys and points/stamps/credit as delta values. The 2000-row limit also restates the schema's maxItems, so the constraint is doubly enforced rather than newly added.

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?

Specific verb+resource ('Preview a bulk customer import') with an explicit scope bound (max 2000 rows) and a stated outcome (matches existing accounts, shows create vs update plus points/stamps/credit deltas). It is unambiguously distinguishable from the sibling commit_customer_import.

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

Usage Guidelines5/5

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

Explicitly routes the agent: this tool previews, then 'Use commit_customer_import with the returned sessionId to apply.' The alternative tool and the condition that selects it are both named, leaving nothing to inference.

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

All FavCRM toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources