Skip to main content
Glama

MCP Server for Coroot

get_application_traces

Retrieve distributed tracing data for an application to analyze request flow and dependencies. Use filters like timestamps or trace_id to manage response size and focus on specific traces.

Instructions

Get distributed traces for an application.

Retrieves distributed tracing data showing request flow through the application and its dependencies.

⚠️ WARNING: This endpoint can return very large responses (100k+ tokens) when retrieving many traces. Consider using time filters or trace_id to limit the response size.

Args: project_id: Project ID app_id: Application ID (format: namespace/kind/name) from_timestamp: Start timestamp (optional, recommended to limit data) to_timestamp: End timestamp (optional, recommended to limit data) trace_id: Specific trace ID to retrieve (optional, returns single trace) query: Search query (optional)

Input Schema

NameRequiredDescriptionDefault
app_idYes
from_timestampNo
project_idYes
queryNo
to_timestampNo
trace_idNo

Input Schema (JSON Schema)

{ "properties": { "app_id": { "title": "App Id", "type": "string" }, "from_timestamp": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "default": null, "title": "From Timestamp" }, "project_id": { "title": "Project Id", "type": "string" }, "query": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Query" }, "to_timestamp": { "anyOf": [ { "type": "integer" }, { "type": "null" } ], "default": null, "title": "To Timestamp" }, "trace_id": { "anyOf": [ { "type": "string" }, { "type": "null" } ], "default": null, "title": "Trace Id" } }, "required": [ "project_id", "app_id" ], "type": "object" }

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/jamesbrink/mcp-coroot'

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