marketsharp-mcp

marketsharp_inquiries_list

Read-onlyIdempotent

List inquiries page by page, filtering by modification date, appointment date, or salesperson to review leads and scheduled appointments.

Instructions

List inquiries (leads) page by page, optionally only those changed in a date range, 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_inquiries_list"
  }
}

Input Schema

Name	Required	Description
`modifiedTo`	No	Only inquiries changed on or before this time. Date/time in the MarketSharp company time zone, e.g. 2026-10-01 or 2026-10-01T08:00:00.
`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.
`modifiedFrom`	No	Only inquiries 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.
`appointmentTo`	No	Only inquiries 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.
`salespersonId`	No	Only inquiries with appointments for this salesperson (employee ID).
`appointmentFrom`	No	Only inquiries 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.
`appointmentRequired`	No	Only inquiries that have an appointment. MarketSharp defaults to true, so pass false to include inquiries with no appointment yet.

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 without prose. The description adds the paging model ("page by page") and that all filters are optional, but says nothing about how multiple filters combine (AND vs OR) or what the default result set contains when no filter is passed — a real behavioral gap.

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 the resource first and the optional filter dimensions trailing; nothing is padding. It is dense with nested clauses, but every clause maps to an actual parameter group, so no tightening is clearly needed.

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?

For an 8-parameter, zero-required listing tool with no output schema, the definition covers all filter axes and paging adequately. However, the "..., or ..." phrasing reads as mutually exclusive alternatives when the filters are in fact combinable, and ordering/default-result behavior is never mentioned, leaving meaningful ambiguity for a listing call.

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%, so every one of the 8 parameters is already documented, including the appointmentRequired default and the 'short page means last page' rule. The description restates the filter families but adds no combination semantics, and its wording "or for one salesperson" obscures that salespersonId filters on appointment ownership rather than inquiry ownership.

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 states a specific verb and resource ("List inquiries (leads)") and enumerates the three optional filter modes plus pagination, so an agent knows exactly what the call returns conceptually. It does not name any sibling (e.g. marketsharp_inquiries_search or marketsharp_inquiries_list_by_contact) to distinguish itself from, which keeps it from 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 Guidelines3/5

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

Use is implied by the phrase "optionally only those...", which tells the agent this is the general enumeration tool and that filters are optional. No when-not guidance and no explicit alternative for keyword-based lookup or contact-scoped listing, so an agent must infer routing from sibling names alone.

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