Skip to main content
Glama
Jambozx

OnlineCyberTools MCP (280+ filterable tools)

network_request_headers

Read-only

Inspect and analyze the HTTP request headers your browser or client sends, including parsed browser and device details, plus a security header audit.

Instructions

Inspect Incoming HTTP Request Headers. Reflects and analyzes the HTTP request headers that the caller's own client sent to this endpoint — it does NOT fetch headers from a remote URL. Use it to see the exact User-Agent, Accept, Accept-Language, Accept-Encoding, Connection, cache, and CORS headers your browser or HTTP client emits, plus a parsed browser/platform/device summary and a present/missing security-header audit. Use my_ip instead to resolve your public IP, browser_fingerprint_viewer for client-side fingerprint surface, or header_analyzer to evaluate response headers of a site. Read-only and non-destructive; contacts no external service; results vary per request so it is not idempotent. Inherits the network category rate limit (30 req/min, 180/hr, 500/day for anonymous callers) and a CAPTCHA challenge above 50 requests/hour. Returns the normalized headers map, request metadata, analysis object, and a raw header string.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
worker_idNoOptional registered healthy worker peer ID. Omit to use the default master-server behavior.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
successNoTrue when inspection completed.
headersNoIncoming request headers, Title-Cased name to comma-joined value.
request_infoNoRequest metadata (method, scheme, host, port, path, query_string, protocol, remote_addr, remote_port, server_addr, server_port, server_software, request_time, request_uri, is_secure, is_xhr).
analysisNoParsed browser info, present/missing security headers, connection details, accepted_types/languages/encodings, and request_type.
raw_headersNoRaw request line plus header lines as a single CRLF-joined string.
Behavior5/5

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

Annotations declare readOnlyHint=true, destructiveHint=false, idempotentHint=false. The description adds context: 'Read-only and non-destructive; contacts no external service; results vary per request so it is not idempotent.' It also details rate limits and CAPTCHA, which are not in annotations.

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?

The description is front-loaded with the main purpose and is well-structured. It is concise but the final sentence listing return fields is a bit dense; however, it still efficiently communicates key information without excess.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the single optional parameter, existence of output schema, and many sibling tools, the description covers all aspects: purpose, parameters, behavior, limitations, and return structure. No gaps remain.

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 100% (1 parameter, fully described). The description adds meaning: 'Omit to use the default master-server behavior.' This clarifies usage beyond the schema field description.

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 uses specific verbs ('Inspect', 'Reflects and analyzes') and clearly states the resource (incoming HTTP request headers). It explicitly distinguishes from sibling tools like my_ip, browser_fingerprint_viewer, and header_analyzer by contrasting their purposes.

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

Usage Guidelines5/5

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

The description provides explicit guidance on when to use the tool ('to see the exact User-Agent...') and when not to use it (it does not fetch headers from a remote URL). It names alternatives (my_ip, browser_fingerprint_viewer, header_analyzer) and describes rate limits and CAPTCHA conditions.

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/Jambozx/onlinecybertools-mcp-server'

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