Skip to main content
Glama

summarize_traffic

Read-only

Groups captured HTTP/HTTPS flows by host, method, path, and status, with optional filters, to return counts and example request IDs for traffic analysis.

Instructions

Group retained flows by exact host, method, path and status. Optional observation_id, host, path substring, method, status, limit (default 30, max 100). Returns counts and example IDs; paths are not inferred route templates.

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": "summarize_traffic"
  }
}

Input Schema

NameRequiredDescriptionDefault
hostNo
pathNo
limitNo
methodNo
statusNo
observation_idNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.2.1

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnly, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral detail: results are counts plus example IDs, limits are capped at 100, and the caveat that paths are not inferred route templates prevents misreading the output as route grouping.

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 sentences, front-loaded with the grouping behavior before the parameter list. Dense and nearly waste-free, though the parenthetical parameter list reads as a compressed enumeration rather than prose.

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 no output schema, the description correctly explains what comes back (counts and example IDs), and it flags the non-routing caveat. Remaining gaps are minor: the meaning of observation_id scoping and whether filters combine with AND are unstated.

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

Parameters3/5

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

Schema description coverage is 0% across six parameters, so the schema supplies no meaning on its own. The description compensates partially: "path substring" clarifies match semantics and "limit (default 30, max 100)" adds a default and ceiling the schema lacks, but host, method, status and observation_id remain unexplained.

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 opens with a specific verb and resource: "Group retained flows by exact host, method, path and status." That aggregation framing plus "Returns counts and example IDs" clearly distinguishes it from a listing tool like search_flows, though it never names that sibling explicitly.

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 signals you use this to count retained flows matching criteria. There is no explicit when-to-use versus search_flows or get_flow, and no statement of prerequisites or expected call context.

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