marketsharp-mcp

marketsharp_employees_list

Read-onlyIdempotent

List salespeople, project managers, and staff with their IDs page by page. Filter by name or active status to find the employees you need.

Instructions

List employees (salespeople, project managers and staff) with their IDs, page by page.

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

Input Schema

Name	Required	Description
`page`	No	Page to return, starting at 1.
`search`	No	Only employees whose name matches this text.
`pageSize`	No	Employees per page (default 100).
`activeOnly`	No	Only active employees (default true).

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.0.0Nov 11, 2026

TDQS

B3.2/5.0

Behavior3/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 that results are paginated and that returned records carry IDs, but says nothing about total counts, ordering, or what happens with large result sets beyond the schema's page caps.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single front-loaded sentence with no filler; the parenthetical employee taxonomy is useful rather than padding. 'Page by page' is slightly loose wording but still communicates pagination efficiently.

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 simple read-only list tool with full schema coverage and rich annotations, this is nearly sufficient – it states the resource and pagination. The main omission is that it never flags the activeOnly default or result ordering, which an agent would want before calling with no filters.

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%, including page, pageSize, search and activeOnly with their defaults, so the schema carries the parameter burden. The description adds no filter semantics beyond the schema – notably it never mentions the default activeOnly=true, which is the most surprising default for callers.

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 names a specific verb and resource ('List employees') and even clarifies who counts as an employee (salespeople, project managers, staff), which an agent cannot infer from the name alone. It does not distinguish itself from sibling list tools such as marketsharp_contacts_list, but the resource is unambiguous.

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 guidance, no prerequisites, and no mention of alternatives like marketsharp_contacts_search or marketsharp_search_global. The only hint is 'page by page', which signals pagination but not tool selection.

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