Skip to main content
Glama

jaeger_list_operations

Read-onlyIdempotent

Retrieve all operation names traced for a service to use as filters in trace searches. Useful for discovering endpoints or methods before searching for specific traces.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYesService name exactly as returned by jaeger_list_services.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
serviceYes
truncatedYes
operationsYes
operations_countYes
Behavior5/5

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

Beyond annotations (readOnly, idempotent), the description adds that output is capped at 500 operations and details the return dict structure. No contradiction 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.

Conciseness5/5

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

Efficiently structured: summary, API wrap, usage guidance, examples, return format. No superfluous text; every sentence adds value.

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 single parameter and simple operation, description fully explains purpose, usage, constraints (500 cap), output structure, and relationship to sibling tools.

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?

The single parameter 'service' is described in schema with 100% coverage. Description adds context that the name must match exactly as returned by jaeger_list_services, adding value beyond 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 clearly states the verb 'List' and resource 'operation names' for a given service. It distinguishes from siblings like jaeger_list_services and jaeger_search_traces.

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?

Provides explicit when-to-use examples (discovering operation names for filtering) and when-not-to-use (when service unknown or name already known), with alternatives suggested (jaeger_list_services).

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