Skip to main content
Glama

jaeger_list_services

Read-onlyIdempotent

Discover all services with traces in Jaeger to find valid service names before searching operations or traces.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
services_countYes
truncatedYes
servicesYes
Behavior5/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, but the description adds context beyond that: no pagination, output capped at 500 services with truncation hint, and wraps a GET endpoint. 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?

The description is well-structured with a clear opening, a technical note, sections for examples and returns. Every sentence is informative, and it is front-loaded with the main purpose.

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 simplicity (no parameters, output schema provided), the description covers all necessary aspects: behavior, usage, limitations, and return format. It is complete and self-contained.

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 input schema has no parameters, and schema description coverage is 100%, so baseline is 3. However, the description adds value by explicitly stating there are no parameters needed and how to call it, making it more helpful than the baseline.

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 lists all services observed by Jaeger, using a specific verb and resource. It distinguishes itself from sibling tools by explaining when to use it and when not to, such as referencing jaeger_list_operations 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?

Explicit usage guidelines are provided, including when to use (e.g., discovering service names, checking if a service is instrumented) and when not to use (e.g., when service name is known or need dependency graph). It also names alternatives like jaeger_search_traces.

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