Skip to main content
Glama
Zeekeey-jpeg

singleops-mcp-server

by Zeekeey-jpeg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Discover SingleOps tools

singleops_discover_tools
Read-onlyIdempotent

List and filter SingleOps tools by domain and read/write type, showing enabled/disabled state so you can discover callable endpoints.

Instructions

List every tool grouped by domain (clients, jobs, visits, reports…), filterable by domain and read/write, with enabled/disabled state. Returns JSON: {totalTools, domains: {: {tools: [{name, kind, enabled, description}]}}}.

Input Schema

NameRequiredDescriptionDefault
typeNoFilter by tool kind.
domainNoResource domain, e.g. "clients", "jobs", "visits", "reports", "invoices".

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4/5.0
Behavior4/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world operation. The description adds useful behavioral context by explaining grouping, filtering, enabled/disabled state, and the exact return shape.

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

Conciseness5/5

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

The description is compact and front-loaded: one sentence covers purpose and filters, and one sentence gives the return structure. There is no wasted text.

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?

Because there is no output schema, the description appropriately supplies the JSON return shape. It covers filters and enabled state, though it could state default behavior when no filters are provided.

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 coverage is 100%, so the input schema already documents both parameters. The description reinforces that results can be filtered by domain and read/write, but it does not clarify the other enum values such as delete, denied, or meta beyond what is already in the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/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: it lists every tool, grouped by domain, with filters. This clearly distinguishes the discovery/meta tool from the many sibling SingleOps API tools.

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?

Usage is implied because this is a discovery tool, but the description does not explicitly say when to call it versus calling a specific sibling tool, nor does it state exclusions or recommended workflow.

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