Skip to main content
Glama

BRAINIAC Web Technology Fingerprinting

Validate security.txt (RFC 9116)

web-technology_security-txt-validate
Read-onlyIdempotent

Validate security.txt Contact/Expires and optional fields per RFC 9116, including expiry and Canonical checks. Price $0.02 USDC. POST /api/v1/web-technology/security-txt-validate. An unpaid call returns the x402 payment terms and does not run.

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": {
      "content": "<content>"
    },
    "name": "web-technology_security-txt-validate"
  }
}

Input Schema

NameRequiredDescriptionDefault
nowNonow, string, date-time. Optional.
contentYescontent, string, length 1 to 100000. Required.
servedAtNoservedAt, string, uri. Optional.

Output Schema

NameRequiredDescriptionDefault
validNovalid. Boolean.
errorsNoerrors. Array.
fieldsNofields. Object.
sourcesNosources. Array.
warningsNowarnings. Array.
limitationsNolimitations. Array.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful behavior beyond them: a $0.02 USDC price, the fact an unpaid call returns x402 payment terms, and that the validation does not execute in that case. It does not discuss output shape, but an output schema exists to carry that.

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?

Roughly one sentence of purpose followed by price, endpoint, and payment behavior — all front-loaded and free of filler. The raw POST path is marginally redundant but conveys transport expectations.

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?

For a single-required-string validation tool with a full output schema and 100% param coverage, the description supplies everything an agent needs: what is checked, the RFC in force, cost, and what happens on an unpaid call.

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 100%, so the three parameters (content, now, servedAt) are already documented in the schema. The description hints at Expires/Canonical checking, which loosely maps to now and servedAt, but adds no format or semantics beyond that, so the baseline 3 applies.

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 names a specific verb (Validate) and resource (security.txt Contact/Expires plus optional fields) and cites RFC 9116, with enough specificity to separate it from siblings such as ads-txt-validate. It stops short of explicitly contrasting with those siblings, but the resource label is distinctive.

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 implied: feed a security.txt document in and get RFC 9116 conformance feedback. There is no explicit when-to-use/when-not-to-use guidance, no statement of prerequisites beyond payment handling, and no reference to alternative tools for related checks.

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