marketsharp-mcp

marketsharp_contacts_list

Read-onlyIdempotent

List contacts page by page, filtered by changes since a date, appointment date range, or salesperson, to sync or review CRM records without bulk exports.

Instructions

List contacts page by page, optionally only those changed since a date or with appointments in a date range or for one salesperson.

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

Input Schema

Name	Required	Description
`pageNumber`	No	Page to return, starting at 1.
`rowsPerPage`	No	Rows per page (default 100). Fewer rows than rowsPerPage means this is the last page.
`appointmentTo`	No	Only contacts with an appointment on or before this time. Date/time in the MarketSharp company time zone, e.g. 2026-10-01 or 2026-10-01T08:00:00.
`modifiedSince`	No	Only contacts changed on or after this time. Date/time in the MarketSharp company time zone, e.g. 2026-10-01 or 2026-10-01T08:00:00.
`salespersonId`	No	Only contacts with appointments for this salesperson (employee ID).
`appointmentFrom`	No	Only contacts with an appointment on or after this time. Date/time in the MarketSharp company time zone, e.g. 2026-10-01 or 2026-10-01T08:00:00.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

B3.4/5.0

Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered. The description adds only that results arrive in pages and that filters are optional; it says nothing about default sort order, result shape, or how multiple filters combine. Modest added value over the annotations.

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

Conciseness4/5

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

A single front-loaded sentence with no filler. The only weakness is that the chosen 'or' construction is compact at the cost of clarity about filter combination.

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?

With 6 optional parameters, no output schema, and read-only annotations, the description covers the main selection criteria adequately. It still omits ordering of results and the AND/OR behavior of simultaneous filters, which materially affect how an agent pages through data.

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?

Schema description coverage is 100%, including time zone and format examples, so the baseline is 3. The description restates the three filter groups but adds no semantics beyond the schema, and its phrasing 'changed since a date or with appointments in a date range or for one salesperson' leaves ambiguous whether the filters are combined with AND or treated as alternatives.

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?

The description uses a specific verb and resource ('List contacts') and enumerates the three filter families (modifiedSince, appointment range, salespersonId). It is clear what the tool returns, but it never differentiates itself from marketsharp_contacts_search or marketsharp_contacts_get, leaving the agent to infer the distinction from names alone.

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?

'Page by page' plus 'optionally only those...' implies this is the enumeration path with optional narrowing, which is usable guidance. However, there is no explicit statement of when to prefer this over the search or get siblings, nor any prerequisites or exclusion conditions.

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