Skip to main content
Glama
avivsinai

langfuse-mcp

find_route_decisions

Find agent route decisions recorded as Langfuse SPAN observations using filters for provider, router, session, and trace. Supports pagination and flexible output.

Instructions

Find generic agent route decisions emitted as Langfuse SPAN observations.

This tool is router-neutral. It only treats observations with
metadata.schema_version == "mcp.route_decision.v1" as route decisions, and
it filters on fields inside observation metadata rather than display output.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
ageNoNumber of minutes to look back (positive integer, max 7 days/10080 minutes)
pageNoPage number for pagination (starts at 1)
limitNoMaximum number of route decisions to return per page
providerNoOptional route-decision metadata provider filter
trace_idNoOptional Langfuse trace ID filter
session_idNoOptional route-decision metadata session_id filter
decision_idNoOptional route-decision metadata decision_id filter
output_modeNoControls the output format and action. 'compact' (default): Returns a summarized JSON object optimized for direct agent consumption. 'full_json_string': Returns the complete, raw JSON data serialized as a string. 'full_json_file': Returns a summarized JSON object AND saves the complete data to a file.compact
router_nameNoOptional route-decision metadata router_name filter
capability_idNoOptional route-decision metadata capability_id filter

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
resultYes
Behavior4/5

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

With no annotations provided, the description carries the full burden. It discloses that the tool treats observations with a specific schema_version and filters on metadata fields, which are behavioral traits beyond what the input schema shows. However, it does not mention performance characteristics or side effects, though the read-only nature is implied.

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 concise with three sentences, front-loading the purpose. Every sentence adds value: the first states the main function, the second clarifies router-neutrality, and the third explains the filtering logic. No wasted words.

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

Completeness4/5

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

The description covers the tool's purpose and filtering behavior, and the input schema fully documents all 10 optional parameters. The presence of an output schema (not shown but indicated) may reduce the need to describe return values. However, it could briefly mention pagination or default output handling, but overall it is adequate.

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?

Given 100% schema description coverage, the baseline is 3. The description adds value by explaining that parameters are filters on 'route-decision metadata' and that the tool filters on 'fields inside observation metadata'. This clarifies the origin and purpose of the parameters beyond the schema descriptions.

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 finds 'generic agent route decisions emitted as Langfuse SPAN observations', specifying the verb 'Find', the resource ('route decisions'), and the context ('Langfuse SPAN observations'). It distinguishes itself from siblings by noting it is 'router-neutral' and filters on metadata schema version, providing a clear purpose.

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

Usage Guidelines4/5

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

The description implicitly guides usage by explaining the tool's router-neutral nature and the filtering criteria (metadata.schema_version). While it does not explicitly state when to use versus alternatives or provide exclusion criteria, it offers sufficient context for an agent to understand the tool's scope among siblings like find_exceptions or get_route_decision.

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/avivsinai/langfuse-mcp'

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