Skip to main content
Glama

net-web-media

har_performance_analyze

Analyze HTTP Archive (.har) JSON waterfalls for total transfer size, slow endpoints, HTTP 4xx/5xx failures, MIME breakdown, and uncompressed payloads.

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

Input Schema

NameRequiredDescriptionDefault
textNo
filePathNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

C2.8/5.0
Behavior2/5

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

With no annotations, the description carries the full burden. It never states that this is a passive read-only analysis, whether the file is fetched from disk or the payload is supplied inline, whether thresholds/limits apply, or how large a HAR it can handle. It only lists the analysis categories, not the behavior.

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?

One tight sentence, front-loaded with the verb and resource, followed by a scannable list of analysis outputs. No filler; the only mild cost is the density of the enumeration, which reads as jargon-heavy but is still efficient.

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?

The enumerated categories double as a partial description of what the report contains, which partly compensates for the missing output schema. However, with zero annotation coverage and zero schema description coverage, an agent still cannot tell how to supply the HAR or what shape the results take, leaving real gaps for a two-parameter analysis tool.

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 0%, so the description must explain the two parameters, but it says nothing about 'text' vs 'filePath' — the single most important ambiguity (inline HAR JSON versus a path) is left entirely unresolved, along with whether both are required or mutually exclusive. The reference to '.har JSON' gives only the faintest hint.

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?

States a specific verb ('Analyze') and resource ('HTTP Archive (.har) JSON waterfalls') and enumerates the concrete metrics produced: total transfer size, slow endpoints, 4xx/5xx, MIME breakdown, uncompressed payloads. This is unambiguous and no sibling tool touches HAR files, so differentiation is implicit rather than stated.

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

Usage Guidelines2/5

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

There is no when-to-use guidance, no prerequisites (e.g. the HAR must be captured with content enabled for size analysis), and no alternatives mentioned. The only context is the implied 'you have a .har file and want performance insight', which the agent must infer.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources