Skip to main content
Glama
Zeekeey-jpeg

singleops-mcp-server

by Zeekeey-jpeg

Get net sales report

singleops_read_get_net_sales_report
Read-onlyIdempotent

Retrieves the SingleOps net sales report, returning filtered, sorted, paginated sales data in markdown or JSON for revenue analysis and reporting.

Instructions

Get net sales report. (GET /reports/net_sales) 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], table_filter_start, table_filter_end, report_range_cache, operation_id, sales_rep_id, 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[]".
operation_idNoQuery parameter "operation_id".
sales_rep_idNoQuery parameter "sales_rep_id".
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).
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]".
table_filter_endNoQuery parameter "table_filter_end".
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]".
report_range_cacheNoQuery parameter "report_range_cache".
table_filter_startNoQuery parameter "table_filter_start".
settings_initializedNoQuery parameter "settings_initialized".
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]".
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

C2.7/5.0
Behavior3/5

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

Annotations already establish readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description does add genuine value by disclosing that the endpoint was inferred from the SingleOps web app's own traffic and results should be confirmed, plus a summary of the return keys. However it says nothing about permissions, pagination defaults, or rate/volume limits on a report that can return large tables.

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 description is front-loaded acceptably, but roughly 80% of its length is a run-on enumeration of 100+ parameter names already present in the schema, which buries the one useful caveat. It is padded rather than concise.

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 106-parameter tool with no output schema, the description should explain the handful of parameters an agent would realistically set and how they interact. Instead it dumps the raw list, leaving the agent unable to distinguish required filtering from optional DataTables plumbing; only the return-key list and reliability caveat are genuinely useful.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is nominally 100%, but every schema property is a tautology ('Query parameter "draw"'), so the schema conveys no real meaning. The description then repeats the identical bare parameter names, adding zero semantics for the parameters that actually matter (table_filter_start/end, report_range_cache, operation_id, sales_rep_id) and never explaining the DataTables draw/start/length or columns[n][search][value] conventions.

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 ('Get net sales report') and anchors it to an endpoint (GET /reports/net_sales), so an agent knows what it returns. It does not differentiate from the many sibling report tools (get_sales_rep_report, get_payment_totals_report, etc.), which matters given how many near-identical names exist.

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 statement of when to use this report versus the dozens of sibling report tools, no prerequisites, and no indication of what filters select this report's data. The only guidance is the caveat 'confirm results', which is a reliability warning rather than usage routing.

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