Skip to main content
Glama

security_txt

Locates and parses RFC 9116 security contact files from a domain's /.well-known/ and root paths to extract contact and policy fields.

Instructions

Look for RFC 9116 security.txt at /.well-known/ and root, parse its fields.

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": {
      "domain": "<domain>"
    },
    "name": "security_txt"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv2.0.0

TDQS

B3.3/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. It does disclose useful behavior beyond the schema by naming the two probe locations (/.well-known/ and root), but says nothing about what happens when the file is absent, whether redirects or HTTP/HTTPS fallbacks are followed, or whether the operation is read-only.

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?

A single front-loaded sentence with zero filler: the action, the standard, the probe locations, and the outcome are all packed into it without redundancy.

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?

For a simple one-parameter read-only lookup with no output schema, the description covers the essentials of what it does but omits the domain format and the not-found/error outcome. Those gaps are minor but real for an agent deciding how to call it.

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 description coverage is 0% for the single required 'domain' parameter, and the description says nothing about its expected format — bare hostname versus a full URL, whether a scheme or port is accepted. The only parameter is therefore left ambiguous.

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?

Names a specific verb ('look for', 'parse') and resource (RFC 9116 security.txt) and even states the exact paths probed, which makes it easy to distinguish from siblings like robots_txt. It stops short of explicitly contrasting itself with any alternative tool, so it sits one notch below a 5.

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 only implied: an agent can infer this is for discovering a domain's published security contact/policy data via the standard file. There is no statement of when to prefer it over siblings like robots_txt or email_security, and no mention of prerequisites or exclusions.

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