Skip to main content
Glama
Sign In

BlackVeil DNS & Email Security Scanner

by com.blackveilsecurity
OverviewDiscussionsAdmin

get_domain_rank

Read-onlyIdempotent

Rank a domain against its country or global cohort using the GSI benchmark corpus. Accepts a domain score (from scan_domain) and optional country/sector; returns a percentile: "scores better than X% of peers". Owner-gate exempt — public cohort data only.

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>",
      "score": "<score>"
    },
    "name": "get_domain_rank"
  }
}

Input Schema

NameRequiredDescriptionDefault
scoreYesDomain score (0–100) from scan_domain. Used to compute the cohort percentile.
domainYesDomain to rank against its cohort (e.g., example.com)
formatNoOutput verbosity.
sectorNoSector label, e.g. "finance". Accepted but not yet used to filter the cohort.
countryNoISO 3166-1 alpha-2 country code to use the country cohort (e.g., "NZ"). Omit for global cohort.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / format / description
      Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."
    • changedInput schema / properties / sector / description
      Previous value: -"Sector label (e.g., \"finance\"). Forwarded to the cohort endpoint; sector filtering is planned for a future release."New value: +"Sector label, e.g. \"finance\". Accepted but not yet used to filter the cohort."
  2. Changed1 schema field changed
    • addedInput schema / additionalProperties
      Added value: +false
  3. Added

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuinely new context beyond that: 'Owner-gate exempt — public cohort data only' tells the agent no ownership/authorization check is required, and it spells out the return shape ('scores better than X% of peers'), which matters since no output schema exists.

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?

Three short sentences, front-loaded with what the tool does, then inputs, then output, then the access caveat. Every clause carries information; nothing is redundant padding.

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 five-parameter read-only ranking tool with full schema coverage and no output schema, the description supplies everything an agent needs: input dependency on scan_domain, cohort selection rule, the percentile return format, and the authorization exemption. No material gap remains.

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 all five parameters are already documented in structured fields and the baseline applies. The description restates the score/country relationship but adds no syntax or edge-case detail, and it labels sector merely 'optional' without echoing the schema's important caveat that sector is accepted but not yet used to filter the cohort.

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?

States a specific verb and resource ('Rank a domain') plus the exact cohort basis ('country or global cohort using the GSI benchmark corpus'), which no sibling tool name implies. The parenthetical '(from scan_domain)' ties it to a concrete upstream sibling, so an agent can tell what this tool is and is not.

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?

Makes the usage context explicit: it needs a score produced by scan_domain, and cohort selection is driven by whether country is supplied ('Omit for global cohort'). It does not state exclusions or when to skip ranking, but the upstream dependency is clearly signposted.

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

All BlackVeil DNS & Email Security Scanner toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources