Skip to main content
Glama

filter_sessions

Filter Fiddler SAZ sessions by host, method, status, URL keyword or regex, body keywords, size, or duration to pinpoint specific HTTP traffic.

Instructions

Search/filter sessions by host, method, status, URL keyword or regex, body keywords, size and duration.

Args: saz_path: Path to the .saz file. host: Substring match on Host[:port]. method: HTTP method, e.g. GET/POST (case-insensitive). status: Exact status code. status_min / status_max: Status code range. url_keyword: Case-insensitive substring of the URL. url_regex: Regex (Python syntax, max 200 chars) matched against the URL. req_body_keyword: Substring search inside the decoded request body. resp_body_keyword: Substring search inside the decoded response body. min_size / max_size: Request+response body size range in bytes. min_ms / max_ms: Total duration range in milliseconds. only_errors: Only 4xx/5xx responses. only_redirects: Only 3xx responses. only_success: Only 2xx responses. with_response: True/False to require/forbid a response. websocket: True/False to require/forbid WebSocket messages. limit: Max sessions returned (1-1000).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
hostNo
limitNo
max_msNo
methodNo
min_msNo
statusNo
max_sizeNo
min_sizeNo
saz_pathYes
url_regexNo
websocketNo
status_maxNo
status_minNo
only_errorsNo
url_keywordNo
only_successNo
with_responseNo
only_redirectsNo
req_body_keywordNo
resp_body_keywordNo
Behavior3/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It adds valuable specifics: case-insensitive substring matches, Python regex syntax with max length 200, decoded body search, and inclusive ranges for size/duration. However, it does not explicitly state that the operation is read-only, nor does it describe the return format or result ordering, which is a notable gap for a tool with no annotation safety hints.

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 a single-purpose opening line followed by a compact argument list. Every line earns its place, with no redundant text or filler. The structure is front-loaded with the tool's purpose, then parameter details, making it easy to scan.

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?

With 20 parameters, no output schema, and no annotations, the description covers parameter semantics comprehensively, but it omits return value details, default limit, and any ordering behavior. It is sufficiently complete for invocation, yet slightly short on post-invocation expectations.

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%, and the description fully compensates by explaining every parameter with concrete semantics: host as substring match, method case-insensitive, regex constraints, range behavior, and limit maximum. This goes well beyond the bare schema titles and provides actionable meaning for each of the 20 parameters.

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 opens with 'Search/filter sessions by...' which clearly names the action (search/filter) and resource (sessions), and enumerates the full set of filtering dimensions. This distinguishes it from siblings like list_sessions (which lists all) and get_session (which fetches a single session), making the purpose unambiguous.

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?

The description implies its usage—any time filtered session lookup is needed—but it does not explicitly state when to prefer this over alternatives like list_sessions or slow_requests, nor does it mention exclusions or prerequisites. The context is clear but the guidance is not explicit.

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/hqzzzz/fiddler-mcp'

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