marketsharp-mcp

marketsharp_notes_list

Read-onlyIdempotent

Retrieve all notes for a MarketSharp contact or filter by a specific note type such as Appointment, Inquiry, or Job. Requires an Employee ID on the connection.

Instructions

List the notes for a contact: all types, or one type such as ContactNote, Appointment, Inquiry or Job. Needs an Employee ID on the connection, and runs with that employee's MarketSharp permissions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "contactId": "<contactId>"
    },
    "name": "marketsharp_notes_list"
  }
}

Input Schema

Name	Required	Description	Default
`noteType`	No	Only this note type.
`contactId`	Yes	MarketSharp contact ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and open-world behavior, so the safety profile is covered. The description adds genuinely new operational context: the call requires an Employee ID on the connection and executes under that employee's MarketSharp permissions, which tells the agent results may be permission-scoped. Return shape and pagination remain unstated.

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 tight sentences: the core action and filter semantics come first, the connection prerequisite second. No filler, and every clause carries information an agent needs before calling.

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 a two-parameter read tool with full schema coverage and annotations, the description covers the action, the optional filter, and the auth precondition. Only the shape of returned notes (fields, ordering, paging) is left unaddressed, and with no output schema that is a modest remaining gap.

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 100%, so the baseline is 3, but the description adds the key semantic that omitting noteType returns all types and that the filter narrows to one, which the schema's terse 'Only this note type.' does not spell out. The illustrative enum values (ContactNote, Appointment, Inquiry, Job) also aid selection.

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 the notes for a contact') plus the scope ('all types, or one type'), which lets an agent distinguish it from sibling list tools like marketsharp_inquiry_notes_list that are scoped to another entity. It doesn't explicitly name a sibling, so it stops short of 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 Guidelines4/5

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

Gives a clear usage condition (list everything, or narrow to a single type) and a prerequisite ('Needs an Employee ID on the connection'). It doesn't state when to prefer a different tool or what to do when no notes exist, so no explicit alternatives or exclusions.

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