Skip to main content
Glama

net_tools_headers_audit

[$x402 pago por llamada] Audita 6 headers de seguridad comunes (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) en una URL.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "url": "<url>"
    },
    "name": "net_tools_headers_audit"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYes
x_paymentNoOpcional. Header X-PAYMENT (x402) ya construido por el cliente/agente llamador. Si se omite, la llamada devuelve 402 con los requisitos de pago, igual que la API HTTP directa.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.2/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, but it does disclose an important behavioral trait upfront: it is an x402 pay-per-call tool, which an agent must know before invoking. However, it does not describe the audit's output (which headers are present/missing/graded), whether follow-redirects or TLS state affect results, or any rate limits, leaving gaps for an unannotated tool.

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?

A single compact sentence listing the six headers is efficient and front-loads the payment model tag. Minor deduction because the payment bracket precedes the actual purpose, slightly delaying what the tool does.

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?

Given no annotations, no output schema, and only two parameters, the description covers what the tool inspects and the payment model, which is enough for correct selection and invocation. It is still thin on the result format and on how the required url must be formed, which an agent would otherwise need to guess.

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 coverage is 50%: the x_payment parameter is well documented in the schema, while url has no schema description. The description only implicitly conveys that url is the audit target ('en una URL'), adding no format, scheme, or host requirements, so it does little to compensate for the undocumented required parameter.

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 states a specific verb ('Audita') and resource (six named security headers: HSTS, CSP, X-Frame-Options, etc.) applied to a URL, which clearly separates it from siblings like net_tools_ssl_check or web_tools_tech_detect. It enumerates the exact header set, leaving no ambiguity about scope, but doesn't explicitly contrast itself with the nearest auditing siblings.

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 statement of when to use this tool versus alternatives such as net_tools_ssl_check, net_tools_redirect_trace, or web_tools_metadata, nor any prerequisites (e.g., URL must include scheme, whether redirects are followed or the final response is audited). The only contextual hint is the payment note.

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