Skip to main content
Glama
Zeekeey-jpeg

singleops-mcp-server

by Zeekeey-jpeg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get payment totals report

singleops_read_get_payment_totals_report
Read-onlyIdempotent

Retrieve SingleOps payment totals by date range and filters, with sorting and pagination, to review payment amounts and report totals.

Instructions

Get payment totals report. (POST /reports/payment_totals_report) Inferred from the SingleOps web app's own traffic; confirm results. Body keys 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], order[0][column], order[0][dir], start, length, search[value], search[regex], table_filter_start, table_filter_end, report_range_cache. Returns JSON with keys: draw, recordsTotal, recordsFiltered, data, meta, table_id, settings. Read-only query sent as POST (filters go in body).

Input Schema

NameRequiredDescriptionDefault
bodyNoRequest body as a JSON object. Match the fields listed in the description.
extra_queryNoAny additional query parameters.
response_formatNoOutput format: "markdown" (default, readable tables) or "json" (full raw response).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description goes beyond them by disclosing that this read is issued as a POST with filters in the body, that the field set was inferred from observed traffic and should be verified, and that the response carries DataTables-style keys. The inference caveat is genuinely valuable context not captured anywhere in structured fields.

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

Conciseness3/5

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

Front-loaded correctly: purpose, endpoint, and the verification caveat come first. However, the ~40-item flat key dump is bulky and unstructured, and a more compact pattern notation (columns[0-4][data|name|searchable|orderable|search][value|regex]) would carry the same information in a fraction of the space.

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 three-parameter report tool with no output schema, the description supplies both the request body shape and the top-level response keys, plus the POST-for-read quirk. An agent can construct a plausible call and interpret the result without further discovery; only per-key semantics and pagination behavior remain unstated.

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

Parameters4/5

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

Schema coverage is 100%, but the body parameter is an open additionalProperties object, so the description's enumeration of the accepted body keys (draw, columns[n][*], order[0][*], start, length, search[*], table_filter_start/end, report_range_cache) is real added value the schema cannot convey. It stops short of explaining what individual keys mean — e.g. table_filter_start/end are presumably date bounds but that is left to inference.

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 ('Get payment totals report') and pins it to the concrete endpoint POST /reports/payment_totals_report. It is distinguishable from most siblings but never differentiates itself from the very similar singleops_read_get_payment_records_report, which an agent would also consider.

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 adjacent payment_records report or the other report tools. The only guidance is a caveat ('confirm results'), which is about trust, not about tool selection.

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