marketsharp-mcp

marketsharp_appointments_list

Read-onlyIdempotent

List appointments page by page, filtered by appointment date range, salesperson, inquiry, or modification date, to quickly see what is scheduled.

Instructions

List appointments page by page by appointment date range, change date range, salesperson or inquiry. Use this for "what's on the schedule".

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_appointments_list"
  }
}

Input Schema

Name	Required	Description
`inquiryIds`	No	Only appointments for these inquiry IDs (at most 100).
`modifiedTo`	No	Only appointments 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 appointments 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	Appointments 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 this salesperson (employee ID).
`appointmentFrom`	No	Appointments 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

A3.8/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 the paging model ("page by page"), already largely spelled out in the rowsPerPage schema, and says nothing about result shape, default-window behavior, or volume. With annotations doing most of the work beyond a paging hint, a 3 fits.

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?

Two short sentences, front-loaded with the operation and its filter axes, then a plain-language use case. Nothing is redundant.

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?

For an eight-parameter, all-optional, read-only list tool with a fully described schema and complete safety annotations, the description covers the essentials, and no output schema is needed since returns are list-shaped. It could add one note that all filters are optional and that an unfiltered call returns the full schedule, but the definition is otherwise sufficient to call correctly.

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 eight parameters is documented with type, format and time-zone notes; the baseline is 3. The description's filter list maps onto those parameters but adds no format or interaction detail (for example, how appointmentFrom/To relate to modifiedFrom/To) beyond what the schema already provides.

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 and resource (list appointments) and enumerates the filter dimensions (appointment date range, change date range, salesperson, inquiry), which lets an agent tell it apart from the by-contact variant in practice. It stops short of naming a sibling explicitly, so it is clear but not maximally differentiated.

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

Usage Guidelines4/5

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

Gives a concrete usage context - "what's on the schedule" - plus pagination framing ("page by page"), which tells the agent this is the browsing/listing entry point. It offers no exclusions or named alternatives, but the supplied context is unambiguous about when to reach for it.

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