marketsharp-mcp

marketsharp_inquiry_notes_list

Read-onlyIdempotent

List inquiry notes or job notes for a MarketSharp inquiry ID, helping you review lead and job activity in one place.

Instructions

List the notes on an inquiry (lead), or on the job created from it. Needs MarketSharp's View Opportunity Note permission.

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": {
      "inquiryId": "<inquiryId>"
    },
    "name": "marketsharp_inquiry_notes_list"
  }
}

Input Schema

Name	Required	Description	Default
`noteType`	No	Inquiry notes (default) or Job notes.
`inquiryId`	Yes	MarketSharp inquiry ID.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

A3.8/5.0

Behavior4/5

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

Annotations already declare read-only, idempotent, non-destructive behavior, so the safety profile is covered. The description adds genuinely new pre-flight context by naming the required MarketSharp permission ('View Opportunity Note'), which an agent cannot learn from the schema and which prevents a predictable authorization failure.

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 with no filler: scope first, prerequisite second. Every clause carries information, and the permission requirement is placed at the end where it reads as a checklist item 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-only list tool with full schema coverage and safety annotations, the definition covers scope, entity mapping, and the permission prerequisite. The only mild gap is that no return-shape or paging expectations are sketched, and no output schema exists to cover that.

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 both parameters, including the Inquiry/Job enum with its default, are already fully documented. The description only reinforces the inquiry-as-lead terminology and the inquiry-to-job relationship, which is marginal added meaning over the schema.

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 on an inquiry (lead), or on the job created from it'), and the parenthetical maps MarketSharp's 'inquiry' to the common 'lead' term. It implicitly distinguishes itself from the broader notes_list by being scoped to a single inquiry or job, though it does not name that sibling.

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?

Usage is implied by the scope statement — use this when you want notes attached to one specific inquiry or its job. There is no explicit when-not guidance or named alternative such as the general notes list, so the agent must infer the routing decision.

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