marketsharp-mcp

marketsharp_jobs_search

Read-onlyIdempotent

Search jobs by job name, number, contact name, business, email, phone, or address using QuickFind; requires an Employee ID on the connection and respects that employee's MarketSharp permissions.

Instructions

Find jobs by job name or number, or by the contact's name, business, email, phone or address (QuickFind). Needs an Employee ID on the connection, and runs with that employee's MarketSharp permissions.

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

Input Schema

Name	Required	Description
`zip`	No	ZIP code.
`city`	No	City.
`state`	No	State, e.g. MI.
`job_name`	No	Job name.
`last_name`	No	Last name, or the start of it.
`first_name`	No	First name, or the start of it.
`job_number`	No	Job number.
`phone_number`	No	Phone number, digits only is fine.
`business_name`	No	Business name.
`email_address`	No	Email address.
`numberOfRecords`	No	Most records to return (default 25).
`address_line_one`	No	Street address line 1.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

A3.7/5.0

Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds non-obvious context beyond that: the call requires an Employee ID on the connection and executes under that employee's MarketSharp permissions, which explains why results can vary by caller. It does not disclose result ordering or what an all-empty search does.

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 tight sentence that front-loads the searchable attributes and closes with the connection prerequisite. Every clause carries information; nothing is repeated from the schema or annotations.

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?

With 12 all-optional parameters and no output schema, the description leaves two meaningful gaps: what a call with no filters returns, and the shape of results beyond 'records'. The permission and prerequisite notes are valuable, but an agent still guesses at behavior at the boundaries.

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% and all 12 parameters are individually documented, so baseline 3 applies. The description groups the parameters into search families (job identifiers vs. QuickFind contact fields) but doesn't clarify whether supplied fields combine as AND filters or are OR'd, nor how partial matching differs between fields.

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 (Find) and resource (jobs) plus the exact search keys: job name, job number, and contact name/business/email/phone/address via QuickFind. An agent can distinguish this from marketsharp_jobs_get by the search framing, though no sibling is named explicitly.

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?

The definition implies when to use it (you have some identifying attribute rather than an ID) and gives a prerequisite (an Employee ID on the connection), but offers no exclusions or comparison to alternatives such as marketsharp_search_global or marketsharp_contacts_search. Usage is inferable but not stated.

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