Skip to main content
Glama
Sign In

BlackVeil DNS & Email Security Scanner

by com.blackveilsecurity
OverviewDiscussionsAdmin

prioritize_portfolio_leads

Read-onlyIdempotent

Rank a brand’s portfolio (or an explicit domain set) into prioritized registrar-partner sales leads by product-gap value × severity. Multi-domain, paid. Reuses map_registrar_products per domain, then ranks. Distinct from map_registrar_products (per-domain product mapping) and batch_scan (raw scores).

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "prioritize_portfolio_leads"
  }
}

Input Schema

NameRequiredDescriptionDefault
brandNoBrand seed apex; discovers the portfolio, derives ownership buckets, then ranks the top candidates.
formatNoOutput verbosity.
domainsNoExplicit domain set to rank (max 10). Ownership bucket = "unknown".
force_refreshNoBypass the cache.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / force_refresh / description
      Previous value: -"Bypass cache and run fresh scans."New value: +"Bypass the cache."
    • changedInput schema / properties / format / description
      Previous value: -"Output verbosity. Auto-detected if omitted."New value: +"Output verbosity."
  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, openWorldHint and destructiveHint=false, so safety is covered. The description still adds real value beyond them: it flags cost ("paid") and, more importantly, that the tool fans out by reusing map_registrar_products per domain, which implies multi-call latency and spend. It stops short of stating rate limits, whether results are cached across runs (the force_refresh param hints at caching but this isn't explained), or how many leads come back.

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?

Three tightly packed sentences, front-loaded with the verb+resource and the cost model, followed by the mechanism, then the differentiation. Slightly telegraphic ("Multi-domain, paid.") but every clause earns its place and nothing is padding.

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?

For a four-parameter, read-only ranking tool with annotations covering safety, the description supplies the missing pieces an agent needs: cost, fan-out mechanism, and sibling differentiation. The main residual gap is return shape - no output schema exists, and "prioritized leads ranked by product-gap value × severity" only gestures at what a lead record contains.

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 baseline is 3, and the description adds little beyond it: the parenthetical "or an explicit domain set" merely restates the relationship between the brand and domains parameters that the schema already documents, including the max-10 cap and the "unknown" ownership bucket. Useful context, not new semantics, and it never addresses what happens when both brand and domains are supplied even though neither is required.

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?

Names a specific verb and resource (rank a brand's portfolio / explicit domain set into prioritized sales leads) and states the ranking basis (product-gap value × severity). It also explicitly demarcates itself from map_registrar_products and batch_scan, so an agent can distinguish it without opening any schema.

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

Usage Guidelines5/5

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

States the operating conditions (multi-domain, paid) and names two alternatives with the condition that selects them: map_registrar_products for per-domain product mapping, batch_scan for raw scores. That is exactly the routing information an agent needs; nothing material is left to inference.

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