Skip to main content
Glama

Domain Armor Scorecard

Get a domain's passive security grade

get_domain_grade
Read-onlyIdempotent

Passive, read-only security grade (A-F, 0-100) for a public domain, from public DNS, email authentication (SPF, DKIM, DMARC), HTTPS/TLS and HTTP response headers. It is not a penetration test, and a good grade is not a security guarantee. Rate limit: 8 calls per minute per client; identical repeat queries are served from a 5 minute cache.

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": "get_domain_grade"
  }
}

Input Schema

NameRequiredDescriptionDefault
domainYesPublic domain to grade. Bare domain or subdomain only, no protocol, path or port. Examples: example.com, mail.google.co.uk.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / $schema
      Previous value: -"http://json-schema.org/draft-07/schema#"New value: +"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / domain / description
      Previous value: -"Public domain to grade, e.g. example.com"New value: +"Public domain to grade. Bare domain or subdomain only, no protocol, path or port. Examples: example.com, mail.google.co.uk."
    • addedInput schema / properties / domain / examples
      Added value: +[
      +  "example.com",
      +  "stripe.com"
      +]
    • addedInput schema / properties / domain / title
      Added value: +"Domain"
  2. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Beyond the annotations, the description discloses important operational behavior: the 8-calls-per-minute client rate limit and 5-minute cache for identical repeat queries. It also explains the data sources and sets expectations by stating that a good grade is not a security guarantee.

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 three focused sentences with no wasted wording. It front-loads the tool's output and scope, then adds only necessary caveats about limitations, rate limits and caching.

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 simple one-parameter tool with no output schema, the description supplies the grade format, data sources, safety caveats, rate limit and caching behavior. Nothing material is missing for an agent to invoke it correctly.

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%, and the schema already documents that the domain must be a bare domain or subdomain with examples and length bounds. The description adds no parameter-specific syntax beyond reinforcing that the target is a public domain, so the baseline of 3 is appropriate.

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 states a specific resource and output: a passive, read-only security grade (A-F, 0-100) for a public domain, derived from named sources including DNS, SPF/DKIM/DMARC, TLS and HTTP headers. It also clearly distinguishes the tool from a penetration test, so an agent can identify exactly what it produces.

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

Usage Guidelines4/5

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

It gives clear context for use on public domains and explicitly excludes penetration testing, which is useful when-not guidance. It does not name alternative tools, but no siblings are supplied, so the scope and exclusions provide adequate routing guidance.

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