Skip to main content
Glama
Zeekeey-jpeg

singleops-mcp-server

by Zeekeey-jpeg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Search clients (server-side table query: paging, sorting, filters)

singleops_read_search_clients
Read-onlyIdempotent

Search clients using server-side table queries with paging, sorting, and filters to retrieve filtered client lists from SingleOps.

Instructions

Search clients (server-side table query: paging, sorting, filters). (GET /clients/data_table) Inferred from the SingleOps web app's own traffic; confirm results. Query params seen: draw, columns[0][data], columns[0][name], columns[0][searchable], columns[0][orderable], columns[0][search][value], columns[0][search][regex], columns[1][data], columns[1][name], columns[1][searchable], columns[1][orderable], columns[1][search][value], columns[1][search][regex], columns[2][data], columns[2][name], columns[2][searchable], columns[2][orderable], columns[2][search][value], columns[2][search][regex], columns[3][data], columns[3][name], columns[3][searchable], columns[3][orderable], columns[3][search][value], columns[3][search][regex], columns[4][data], columns[4][name], columns[4][searchable], columns[4][orderable], columns[4][search][value], columns[4][search][regex], columns[5][data], columns[5][name], columns[5][searchable], columns[5][orderable], columns[5][search][value], columns[5][search][regex], columns[6][data], columns[6][name], columns[6][searchable], columns[6][orderable], columns[6][search][value], columns[6][search][regex], columns[7][data], columns[7][name], columns[7][searchable], columns[7][orderable], columns[7][search][value], columns[7][search][regex], columns[8][data], columns[8][name], columns[8][searchable], columns[8][orderable], columns[8][search][value], columns[8][search][regex], columns[9][data], columns[9][name], columns[9][searchable], columns[9][orderable], columns[9][search][value], columns[9][search][regex], columns[10][data], columns[10][name], columns[10][searchable], columns[10][orderable], columns[10][search][value], columns[10][search][regex], columns[11][data], columns[11][name], columns[11][searchable], columns[11][orderable], columns[11][search][value], columns[11][search][regex], columns[12][data], columns[12][name], columns[12][searchable], columns[12][orderable], columns[12][search][value], columns[12][search][regex], columns[13][data], columns[13][name], columns[13][searchable], columns[13][orderable], columns[13][search][value], columns[13][search][regex], columns[14][data], columns[14][name], columns[14][searchable], columns[14][orderable], columns[14][search][value], columns[14][search][regex], order[0][column], order[0][dir], start, length, search[value], search[regex], sales_rep_ids[], show_inactive_clients, show_on_hold_clients, colReorder[], settings_initialized. Returns JSON with keys: draw, recordsTotal, recordsFiltered, data, meta, table_id, settings.

Input Schema

NameRequiredDescriptionDefault
drawNoQuery parameter "draw".
startNoQuery parameter "start".
lengthNoQuery parameter "length".
extra_queryNoAny additional query parameters.
colReorder[]NoQuery parameter "colReorder[]".
order[0][dir]NoQuery parameter "order[0][dir]".
search[regex]NoQuery parameter "search[regex]".
search[value]NoQuery parameter "search[value]".
response_formatNoOutput format: "markdown" (default, readable tables) or "json" (full raw response).
sales_rep_ids[]NoQuery parameter "sales_rep_ids[]".
columns[0][data]NoQuery parameter "columns[0][data]".
columns[0][name]NoQuery parameter "columns[0][name]".
columns[1][data]NoQuery parameter "columns[1][data]".
columns[1][name]NoQuery parameter "columns[1][name]".
columns[2][data]NoQuery parameter "columns[2][data]".
columns[2][name]NoQuery parameter "columns[2][name]".
columns[3][data]NoQuery parameter "columns[3][data]".
columns[3][name]NoQuery parameter "columns[3][name]".
columns[4][data]NoQuery parameter "columns[4][data]".
columns[4][name]NoQuery parameter "columns[4][name]".
columns[5][data]NoQuery parameter "columns[5][data]".
columns[5][name]NoQuery parameter "columns[5][name]".
columns[6][data]NoQuery parameter "columns[6][data]".
columns[6][name]NoQuery parameter "columns[6][name]".
columns[7][data]NoQuery parameter "columns[7][data]".
columns[7][name]NoQuery parameter "columns[7][name]".
columns[8][data]NoQuery parameter "columns[8][data]".
columns[8][name]NoQuery parameter "columns[8][name]".
columns[9][data]NoQuery parameter "columns[9][data]".
columns[9][name]NoQuery parameter "columns[9][name]".
order[0][column]NoQuery parameter "order[0][column]".
columns[10][data]NoQuery parameter "columns[10][data]".
columns[10][name]NoQuery parameter "columns[10][name]".
columns[11][data]NoQuery parameter "columns[11][data]".
columns[11][name]NoQuery parameter "columns[11][name]".
columns[12][data]NoQuery parameter "columns[12][data]".
columns[12][name]NoQuery parameter "columns[12][name]".
columns[13][data]NoQuery parameter "columns[13][data]".
columns[13][name]NoQuery parameter "columns[13][name]".
columns[14][data]NoQuery parameter "columns[14][data]".
columns[14][name]NoQuery parameter "columns[14][name]".
settings_initializedNoQuery parameter "settings_initialized".
show_on_hold_clientsNoQuery parameter "show_on_hold_clients".
columns[0][orderable]NoQuery parameter "columns[0][orderable]".
columns[1][orderable]NoQuery parameter "columns[1][orderable]".
columns[2][orderable]NoQuery parameter "columns[2][orderable]".
columns[3][orderable]NoQuery parameter "columns[3][orderable]".
columns[4][orderable]NoQuery parameter "columns[4][orderable]".
columns[5][orderable]NoQuery parameter "columns[5][orderable]".
columns[6][orderable]NoQuery parameter "columns[6][orderable]".
columns[7][orderable]NoQuery parameter "columns[7][orderable]".
columns[8][orderable]NoQuery parameter "columns[8][orderable]".
columns[9][orderable]NoQuery parameter "columns[9][orderable]".
show_inactive_clientsNoQuery parameter "show_inactive_clients".
columns[0][searchable]NoQuery parameter "columns[0][searchable]".
columns[10][orderable]NoQuery parameter "columns[10][orderable]".
columns[11][orderable]NoQuery parameter "columns[11][orderable]".
columns[12][orderable]NoQuery parameter "columns[12][orderable]".
columns[13][orderable]NoQuery parameter "columns[13][orderable]".
columns[14][orderable]NoQuery parameter "columns[14][orderable]".
columns[1][searchable]NoQuery parameter "columns[1][searchable]".
columns[2][searchable]NoQuery parameter "columns[2][searchable]".
columns[3][searchable]NoQuery parameter "columns[3][searchable]".
columns[4][searchable]NoQuery parameter "columns[4][searchable]".
columns[5][searchable]NoQuery parameter "columns[5][searchable]".
columns[6][searchable]NoQuery parameter "columns[6][searchable]".
columns[7][searchable]NoQuery parameter "columns[7][searchable]".
columns[8][searchable]NoQuery parameter "columns[8][searchable]".
columns[9][searchable]NoQuery parameter "columns[9][searchable]".
columns[10][searchable]NoQuery parameter "columns[10][searchable]".
columns[11][searchable]NoQuery parameter "columns[11][searchable]".
columns[12][searchable]NoQuery parameter "columns[12][searchable]".
columns[13][searchable]NoQuery parameter "columns[13][searchable]".
columns[14][searchable]NoQuery parameter "columns[14][searchable]".
columns[0][search][regex]NoQuery parameter "columns[0][search][regex]".
columns[0][search][value]NoQuery parameter "columns[0][search][value]".
columns[1][search][regex]NoQuery parameter "columns[1][search][regex]".
columns[1][search][value]NoQuery parameter "columns[1][search][value]".
columns[2][search][regex]NoQuery parameter "columns[2][search][regex]".
columns[2][search][value]NoQuery parameter "columns[2][search][value]".
columns[3][search][regex]NoQuery parameter "columns[3][search][regex]".
columns[3][search][value]NoQuery parameter "columns[3][search][value]".
columns[4][search][regex]NoQuery parameter "columns[4][search][regex]".
columns[4][search][value]NoQuery parameter "columns[4][search][value]".
columns[5][search][regex]NoQuery parameter "columns[5][search][regex]".
columns[5][search][value]NoQuery parameter "columns[5][search][value]".
columns[6][search][regex]NoQuery parameter "columns[6][search][regex]".
columns[6][search][value]NoQuery parameter "columns[6][search][value]".
columns[7][search][regex]NoQuery parameter "columns[7][search][regex]".
columns[7][search][value]NoQuery parameter "columns[7][search][value]".
columns[8][search][regex]NoQuery parameter "columns[8][search][regex]".
columns[8][search][value]NoQuery parameter "columns[8][search][value]".
columns[9][search][regex]NoQuery parameter "columns[9][search][regex]".
columns[9][search][value]NoQuery parameter "columns[9][search][value]".
columns[10][search][regex]NoQuery parameter "columns[10][search][regex]".
columns[10][search][value]NoQuery parameter "columns[10][search][value]".
columns[11][search][regex]NoQuery parameter "columns[11][search][regex]".
columns[11][search][value]NoQuery parameter "columns[11][search][value]".
columns[12][search][regex]NoQuery parameter "columns[12][search][regex]".
columns[12][search][value]NoQuery parameter "columns[12][search][value]".
columns[13][search][regex]NoQuery parameter "columns[13][search][regex]".
columns[13][search][value]NoQuery parameter "columns[13][search][value]".
columns[14][search][regex]NoQuery parameter "columns[14][search][regex]".
columns[14][search][value]NoQuery parameter "columns[14][search][value]".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description's one genuine addition is provenance and reliability ('inferred from traffic; confirm results'), which is valuable. It omits DataTables mechanics an agent must know: draw echoed for de-duplication, start/length paging defaults, and the distinction between recordsTotal and recordsFiltered.

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

Conciseness2/5

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

The first sentence and the trailing return-keys sentence are well-placed, but the body is a ~100-item verbatim dump of query parameter names that duplicates the schema and buries the genuinely useful caveat. Roughly 90% of the text earns no place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a 104-parameter, nested, annotation-light-on-semantics tool with no output schema, the description should tell the agent the minimal viable call (e.g., start/length, optional search[value], optional rep/inactive filters) and what 'data' rows contain. It lists return keys but gives no guidance on columns[0..14] meaning, which is the crux of using a DataTables endpoint correctly.

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 nominally 100%, but the schema's own descriptions are placeholders ('Query parameter "draw".'), and the description merely repeats that same list verbatim without adding semantics — it never explains what start/length, draw, search[value], show_inactive_clients, or sales_rep_ids[] actually do. Baseline 3 applies since the structured field nominally covers every parameter, but no real meaning is added.

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?

Opens with a specific verb and resource ('Search clients') plus the mechanism ('server-side table query: paging, sorting, filters') and the HTTP route. It does not distinguish itself from client-adjacent siblings such as singleops_read_lead_list_clients_search_by_field or the various list_client_* tools, so an agent still has to guess which client-search surface to use.

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?

'Server-side table query' implies the large-table / paginated scenario, and the 'Inferred from ... confirm results' note hints at caution, but there is no explicit when-to-use, when-not, or named alternative. With dozens of sibling list/search tools, the absence of routing guidance is a real gap.

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

Deploy Server

Other Tools