Jaeger MCP vs SigNoz MCP Server

Jaeger MCP tools 15

• jaeger_list_servicesList all services that Jaeger has observed traces for. Wraps ``GET /api/services``. Jaeger returns all services at once — no pagination. Output is capped at 500 services with a truncation hint. Use this first to discover valid service names before calling ``jaeger_list_operations`` or ``jaeger_search_traces``. Examples: - Use when: "What services does Jaeger know about?" → call with no parameters; read the ``services`` list. - Use when: "Is `payment-service` instrumented?" → check if `payment-service` appears in the services list. - Use when: Starting a debugging session — list services first, then pick one for ``jaeger_list_operations`` or ``jaeger_search_traces``. - Don't use when: You already know the service name and want to search its traces (call ``jaeger_search_traces`` directly). - Don't use when: You want the dependency graph between services (call ``jaeger_get_dependencies``). Returns: dict with keys ``services_count`` / ``truncated`` / ``services``.
• jaeger_list_operationsList all operation names Jaeger has seen for a given service. Wraps ``GET /api/services/{service}/operations``. Useful for discovering which operation names to pass as filters to ``jaeger_search_traces``. Output is capped at 500 operations. Examples: - Use when: "What HTTP endpoints does `order-service` expose in tracing?" → ``service='order-service'``. - Use when: You want to search for a specific slow operation but need the exact name — list operations first, then pass it to ``jaeger_search_traces``. - Use when: Auditing which gRPC methods a service traces. - Don't use when: You don't have a specific service — start with ``jaeger_list_services`` first. - Don't use when: You want to search traces immediately (skip this step if you already know the operation name). Returns: dict with ``service`` / ``operations_count`` / ``truncated`` / ``operations`` (sorted alphabetically).
• jaeger_search_tracesSearch Jaeger traces with rich filters. Wraps ``GET /api/traces``. Returns a list of trace summaries — use ``jaeger_get_trace`` to drill into a specific trace for span details. The ``tags`` parameter accepts a JSON string so the LLM can construct arbitrary tag filters. Durations (``min_duration``/``max_duration``) are forwarded as-is to Jaeger (e.g. ``'100ms'``, ``'1.5s'``). Examples: - Use when: "Show me recent 500 errors in `order-service`" → ``service='order-service'``, ``tags='{"http.status_code":"500"}'``. - Use when: "Find slow traces (>1s) for `checkout` endpoint" → ``service='checkout'``, ``operation='POST /checkout'``, ``min_duration='1s'``. - Use when: "Give me the last 5 traces in the last hour" → ``limit=5``, set ``start`` to (now - 3600s) in microseconds. - Don't use when: You already have a traceID and want full details (call ``jaeger_get_trace`` directly — one fewer round trip). - Don't use when: You want service dependency topology (call ``jaeger_get_dependencies``). Returns: dict with ``service`` / ``operation`` / ``returned`` / ``truncated`` / ``traces`` (list of :class:`TraceSummary`).