Skip to main content
Glama
Zeekeey-jpeg

singleops-mcp-server

by Zeekeey-jpeg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Get equipment utilization report

singleops_read_get_equipment_utilization_report
Read-onlyIdempotent

Retrieve equipment utilization report data from SingleOps to analyze usage by date range, with sortable and filterable columns and markdown or JSON output.

Instructions

Get equipment utilization report. (GET /reports/equipment_utilization) 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], order[0][column], order[0][dir], start, length, search[value], search[regex], table_filter_start, table_filter_end, report_range_cache, 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).
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]".
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[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[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]".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the safety profile is covered. The description adds useful context that the endpoint was inferred from app traffic and that results should be confirmed, plus the top-level return keys.

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 front-loads the purpose and endpoint well, but it then dumps dozens of raw query parameter names in a single run-on list. Much of that list is redundant with the schema and makes the description unnecessarily bloated.

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?

It provides the endpoint, a reliability caveat, a raw parameter list, and top-level JSON return keys, which helps because there is no output schema. However, for an 86-parameter report tool it does not explain report content, key filters, defaults, or the markdown/json response_format behavior.

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%, so the baseline is 3. The description lists the query parameters seen and the return keys, but it does not explain what the DataTables-style parameters mean or how key filters like table_filter_start and table_filter_end should be used.

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 states a specific verb and resource: 'Get equipment utilization report' and gives the endpoint path. It is clear what report is being fetched, though it does not explicitly distinguish this report from the many sibling report tools beyond the resource name.

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?

The only guidance is 'Inferred from the SingleOps web app's own traffic; confirm results,' which is a reliability caveat rather than when-to-use guidance. It does not name alternatives or explain when this report should be chosen over other report tools.

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