Skip to main content
Glama

search_flows

Read-only

Find retained HTTP/HTTPS flow metadata by observation ID, exact host, path substring, method, or status to analyze captured API traffic; browse newest-first results with cursor pagination.

Instructions

Search retained flow metadata by observation_id, exact host, path substring, method and status. Newest revision first. limit default 30 max 100. For pagination retain after_cursor and set before_cursor to next_before_cursor. reset indicates cursor history loss; snapshot fallback may contain older flows.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "search_flows"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo
pathNo
limitNo
methodNo
statusNo
after_cursorNo
before_cursorNo
observation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A4/5.0
Behavior4/5

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

Annotations already cover the safety profile (readOnly, non-destructive, closed-world), so the description correctly spends its budget elsewhere: result ordering ("Newest revision first"), limit bounds, cursor pagination workflow, and the reset/snapshot-fallback caveat that warns results may be stale or incomplete. That is real behavioral context beyond the annotations, though it never states whether multiple filters are ANDed or what the response envelope looks like.

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?

Four short sentences, front-loaded with the filter list, then ordering, then pagination mechanics and the failure caveat — a sensible order with little waste. The one rough spot is "reset indicates cursor history loss," which is telegraphic and doesn't say where that flag appears given there is no output schema.

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?

For an eight-parameter search tool with no output schema and no parameter descriptions, the definition covers filtering, ordering, limits, pagination and a degraded-result warning, which is nearly everything needed to invoke it correctly. It stops short of explaining filter combination semantics or the shape of returned flows, which an agent would still have to discover.

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

Parameters5/5

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

Schema description coverage is 0%, so the description must carry all parameter meaning and largely does: host is matched exactly, path is a substring match, method and status filter, limit defaults to 30 with a max of 100, and the after_cursor/before_cursor pair is explained with the "retain after_cursor, set before_cursor to next_before_cursor" pagination rule. Only observation_id is left at its self-evident meaning.

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

Purpose4/5

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

The description names a specific verb and resource ("Search retained flow metadata") and enumerates the exact filter dimensions: observation_id, exact host, path substring, method and status. That is much clearer than the bare name, but it never distinguishes this tool from siblings such as get_flow or wait_for_flows, so an agent must infer that this is the multi-filter listing tool.

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 filter list and "retained" wording suggest you use this when you need to narrow flows by host/path/method/status rather than fetch a known flow. There is no explicit when-to-use statement, no exclusion against get_flow or wait_for_flows, and no stated prerequisites.

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