Skip to main content
Glama

analyze_user_flows

Read-onlyIdempotent

Capture runtime route evidence from authorized apps to document user journeys and author flows that static scanning cannot verify.

Instructions

Return actual route evidence for a client to author flows. Static scanning cannot verify runtime journeys.

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": {
      "project": "<project>"
    },
    "name": "analyze_user_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
projectYes

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so safety is covered. The description adds that this examines runtime behavior rather than static code, which hints at a heavier, environment-dependent operation, but leaves critical details unstated — whether a live client/browser is launched, whether a dev server must be running, and how long it takes.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

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

Two tight sentences with no filler, front-loading the output and following with the rationale. Slightly cryptic phrasing costs a bit, but nothing is wasted.

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?

An output schema exists, so return values needn't be described, and annotations cover the safety profile. However, for a runtime-analysis tool the description should say what 'a client' means and what preconditions exist before invocation; that gap is material given the sibling set contains both static and dynamic analysis tools.

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?

There is one required parameter, 'project', with 0% schema description coverage, so the description carries the full burden — yet it never mentions the parameter at all. It doesn't clarify whether 'project' is a name, path, or ID, nor how it relates to the 'client' being analyzed.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The verb 'Return' plus 'route evidence' gives a rough idea, and the second sentence implies contrast with static scanning (likely discover_routes), but 'route evidence' and 'author flows' are internal jargon that don't concretely state what comes back. An agent can guess it obtains runtime route data for a project, but not confidently enough to distinguish it from capture_user_flow or discover_routes.

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

Usage Guidelines3/5

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

Usage is only implied: the statement that 'Static scanning cannot verify runtime journeys' hints this tool is the choice when static analysis is insufficient. No explicit when-to-use condition, no named alternative, and no prerequisites (e.g. app must be running) are stated.

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