get_headers
Read-onlyIdempotent
The caller's HTTP request headers, echoed back (proxy and Cloudflare headers filtered out).
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
IP Address API
by app.ip
TDQS
A4.3/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint. The description adds that proxy and Cloudflare headers are filtered out, providing useful behavioral context beyond annotations.
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 sentence of 11 words, concise and front-loaded with key information.
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?
With no parameters, no output schema, and annotations covering safety, the description fully explains the tool's purpose and behavior.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters4/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There are no parameters, and the schema coverage is 100%. The description adds meaning by explaining what is returned, which is sufficient since no parameter information is needed.
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 clearly states the tool returns the caller's HTTP request headers with specific filtering, distinguishing it from sibling tools like get_asn or get_ip.
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 usage by describing what is returned, but it does not provide explicit guidance on when to use this tool versus alternatives.
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.
TDQS
A4.2/5.0
Disambiguation5/5
Each tool targets a unique aspect of the caller's request or IP information (ASN, headers, IP, location, security, timezone, user agent, coordinates) with no overlap.
Naming Consistency5/5
All tools follow a consistent 'get_' prefix followed by a clear noun (e.g., get_asn, get_headers), making naming predictable and uniform.
Tool Count5/5
With 8 tools, the server provides a focused set of self-service IP and request data operations without being sparse or bloated.
Completeness5/5
The tool set covers all typical aspects of a caller's IP/request information (IP, location, timezone, security, headers, user agent, ASN, coordinates) with no obvious gaps.