Flowlines - MCP Analytics

Aggregate session metrics

aggregate_sessions

Read-onlyIdempotent

Aggregate sessions inside Flowlines at a stable snapshot. Use this for grouped totals and rates instead of downloading sessions through list_sessions.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "reason": "<reason>",
      "user_intent": "<user_intent>",
      "namespace_id": "<namespace_id>",
      "range": "<range>",
      "group_by": "<group_by>",
      "metrics": "<metrics>"
    },
    "name": "aggregate_sessions"
  }
}

Input Schema

Name	Required	Description
`limit`	No	Page size. Defaults to 20.
`range`	Yes	Preset aggregation window ending at the snapshot time. all includes all available history. Custom from/to timestamps are not supported by this tool.
`cursor`	No	Opaque cursor from a previous page.
`reason`	Yes	A short phrase saying why you are calling this tool, for example: find unpaid invoices.
`filters`	No
`metrics`	Yes	Metrics to compute per group.
`group_by`	Yes	Dimensions to group by.
`order_by`	No
`cohort_ids`	No
`user_intent`	Yes	One sentence describing what the user is trying to accomplish. Keep it the same across calls until the user's goal changes.
`namespace_id`	Yes	Flowlines namespace UUID.
`include_unidentified`	No

Output Schema

Name	Required	Description	Default
`data`	Yes
`notice`	No
`truncation`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 19, 2026

TDQS

A3.8/5.0

Behavior3/5

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is fully covered. The description's one addition, the 'stable snapshot' consistency guarantee, is genuinely useful behavioral context, but pagination, result limits, and large-range behavior are left to the schema.

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?

Two tightly written sentences, front-loaded with purpose before the alternative-tool guidance. No filler or redundant restatement of the name.

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

Completeness3/5

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

For a 12-parameter tool with nested filter objects, enums, and grouping semantics, the description is thin on how group_by and metrics interact and on pagination limits. The output schema and annotations cover return values and safety, but the behavioral/parameter guidance an agent needs for complex calls is only partially present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 67%, so roughly a third of parameters (order_by, cohort_ids, include_unidentified, analysis_status, intent_family) are undocumented in either place. The description adds no parameter-level meaning beyond the vague 'grouped totals and rates,' so it does not compensate for the gap.

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?

States a specific verb and resource ('Aggregate sessions inside Flowlines') and explicitly contrasts itself with the sibling list_sessions, so an agent can distinguish it without opening either schema. The 'stable snapshot' framing sharpens what the aggregation operates on.

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?

Gives a clear use condition ('grouped totals and rates') and names the alternative to avoid ('downloading sessions through list_sessions'), which is strong routing guidance. It stops short of explicit when-not edge cases (e.g., single-session lookups should go to get_session) or prerequisites.

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

All Flowlines - MCP Analytics tools Inspect

Try in Browser

Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?