SyncroMSP MCP Server

customers_list

Retrieve a paginated list of customers with optional filters by name, email, business, or ID.

Instructions

List customers with optional filters. Returns paginated results.

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": "customers_list"
  }
}

Input Schema

Name	Required	Description
`id`	No	Filter by specific IDs
`page`	No	Page number
`sort`	No	Sort field
`email`	No	Filter by email
`query`	No	Search query
`lastname`	No	Filter by last name
`firstname`	No	Filter by first name
`business_name`	No	Filter by business name
`include_disabled`	No	Include disabled customers (true/false)

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.1May 26, 2026

TDQS

A3.7/5.0

Behavior3/5

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

No annotations are provided, so the description carries full disclosure burden. It informs that the tool lists customers with filters and returns paginated results, which implies a read operation. However, it does not disclose specifics like default sorting, pagination limits, or whether filters are exact matches, leaving gaps in behavioral understanding.

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 extremely concise, consisting of two short sentences that convey the essential information without any superfluous words. Every word earns its place.

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?

Given the tool has 9 optional parameters and no output schema, the description is adequate but not fully complete. It covers the core functionality but lacks details on pagination behavior, return format, or how filters interact. For a simple list tool, this is minimally viable, but there is room for improvement.

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 has 100% coverage with descriptions for all 9 parameters. The overall description adds no parameter-specific details beyond stating 'optional filters' and 'paginated results,' so it meets the baseline but does not provide additional semantic value.

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 'List customers with optional filters. Returns paginated results,' which identifies the action (list), the resource (customers), and key features (filters, pagination). This distinguishes it from sibling tools like customers_get (single customer) and customers_autocomplete (autocomplete suggestions).

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 implies usage for retrieving a filtered, paginated list of customers but does not explicitly state when to use this tool over alternatives like customers_get or customers_latest. No when-not or alternative guidance is provided, only implied scope.

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

Deploy Server