marketsharp-mcp

marketsharp_inquiries_list_by_contact

Read-onlyIdempotent

Lists every inquiry (lead) for a MarketSharp contact, with an option to include inquiries that have no appointment yet.

Instructions

List every inquiry (lead) for one contact.

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

Input Schema

Name	Required	Description	Default
`contactId`	Yes	MarketSharp contact ID.
`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.3/5.0

Behavior3/5

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

The annotations already declare read-only, idempotent, non-destructive, open-world behavior, so safety is covered. The description adds no behavioral context of its own and its wording ('List every inquiry') sits slightly at odds with the schema's default appointmentRequired=true, which silently excludes inquiries that have no appointment unless false is passed.

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?

A single short sentence, front-loaded with the verb and resource, with the parenthetical clarifying 'lead' without padding. Nothing here is wasted.

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?

The tool is simple (two params, no output schema, safe annotations), so a terse description is defensible, but it omits the one behavior an agent could get wrong, that results are filtered by appointment by default, and gives no guidance on choosing between sibling inquiry tools.

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%: contactId is described as the MarketSharp contact ID and appointmentRequired explains the true-default and the need to pass false. The description adds no parameter meaning beyond that, so the baseline of 3 applies.

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 ('List') and resource ('inquiry (lead)') with a stated scope ('for one contact'), and even clarifies the domain synonym lead = inquiry. It does not name a sibling, so the agent must infer from the scope phrase alone why this differs from marketsharp_inquiries_list or marketsharp_inquiries_search.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance: nothing says to pick this over marketsharp_inquiries_list, marketsharp_inquiries_search, or marketsharp_inquiries_get. The only usage-relevant nuance, the appointmentRequired default, lives in the schema rather than the description.

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