Skip to main content
Glama
mshegolev

jaeger-mcp

by mshegolev

jaeger_search_traces

Read-onlyIdempotent

Search distributed tracing data in Jaeger using filters for service, operation, tags, duration, and time range to identify performance issues or errors.

Instructions

Search 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).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesService name to search traces for (required). Use jaeger_list_services to discover valid names.
operationNoOperation name filter (optional). Use jaeger_list_operations to discover valid names. Example: 'GET /api/orders' or 'grpc.health.v1.Health/Check'.
tagsNoJSON string of tag key-value pairs to filter by (optional). Example: '{"http.status_code":"500"}' to find 5xx errors, or '{"error":"true"}' for any error spans.
startNoStart time in microseconds since Unix epoch UTC (optional). Example: 1713400000000000 for 2024-04-18 00:00:00 UTC.
endNoEnd time in microseconds since Unix epoch UTC (optional). If omitted and start is set, defaults to now.
min_durationNoMinimum trace duration filter (optional). Format: '100ms', '1.5s', '2m'. Use to find slow traces.
max_durationNoMaximum trace duration filter (optional). Format: '100ms', '500ms'. Use to find fast traces or exclude outliers.
limitNoMaximum number of traces to return (1-1500, default 20).

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYes
operationYes
returnedYes
truncatedYes
tracesYes
Behavior4/5

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

Annotations already cover read-only, non-destructive, idempotent, and open-world hints, so the description adds valuable context beyond these: it explains that the tool 'Returns a list of trace summaries' and references jaeger_get_trace for drill-down, clarifies that tags parameter accepts JSON strings, and notes duration formats are forwarded as-is. No contradictions with annotations.

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

Conciseness4/5

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

The description is well-structured with clear sections (purpose, wrapper note, returns, examples, usage guidelines) and uses bullet points for readability. It's slightly verbose but each sentence adds value, such as practical examples and sibling tool references, earning its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (8 parameters, rich filtering), the description is complete: it explains the tool's role in the workflow (search vs. drill-down), provides concrete examples, clarifies parameter nuances (JSON tags, duration formats), and references sibling tools. With annotations covering safety and an output schema existing, no critical gaps remain.

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 schema already documents all parameters thoroughly. The description adds minimal extra semantics: it mentions tags accept JSON strings and durations are forwarded as-is, but doesn't provide significant additional meaning beyond the schema. Baseline 3 is appropriate given high schema coverage.

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 clearly states the tool's purpose: 'Search Jaeger traces with rich filters.' It specifies the verb ('Search'), resource ('Jaeger traces'), and scope ('with rich filters'), distinguishing it from sibling tools like jaeger_get_trace (for specific trace details) and jaeger_get_dependencies (for service topology).

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides explicit usage guidance with 'Use when' and 'Don't use when' examples, including clear alternatives: use jaeger_get_trace for trace details when traceID is known, and use jaeger_get_dependencies for service dependency topology. This directly helps the agent choose between sibling tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mshegolev/jaeger-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server