Skip to main content
Glama

OmniForge Launch Audit MCP

3-in-1 Startup & Domain Launch Readiness Audit

full_launch_readiness_audit
Read-onlyIdempotent

Run a comprehensive, parallel 3-pillar pre-launch audit on a production domain — combining brand/trademark conflict screening, SPF/DKIM/DMARC/DNSBL email deliverability verification, and AI search (robots.txt, /llms.txt, Schema.org JSON-LD) readiness into one unified 0-100 Launch Scorecard and prioritized remediation checklist. Reach for this tool when preparing a domain for launch or diagnosing overall technical growth readiness; use the specialized single-pillar tools when iterating on just one area.

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

Input Schema

NameRequiredDescriptionDefault
domainYesPrimary production domain to audit (e.g. 'resend.com' or 'acme.io').
brandNameNoOptional brand label if different from the domain's second-level label.

Output Schema

NameRequiredDescriptionDefault
domainYesNormalized production domain.
pillarsYesPer-pillar scores and key indicators.
checkedAtYesISO-8601 UTC timestamp.
overallGradeYesOverall letter grade from A to D.
overallScoreYesWeighted 0-100 Launch Readiness Score.
bundleUpgradeNoLinks to the 3-in-1 Pro CLI & CI remediation bundle.
prioritizedFixesYesOrdered list of highest-impact fixes.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

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 adds that the three pillars run in parallel and are combined into a unified scorecard. It does not mention runtime expectations, rate limits, or what happens on unreachable/invalid domains, which is a gap for a network-dependent audit, but the composite behavior is well disclosed.

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?

Two sentences, front-loaded with the capability before the routing guidance. The first sentence is dense with nested parentheticals, but each clause carries distinct information (pillar names, check types, output artifact) rather than filler.

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?

With an output schema present, return values need not be explained, and annotations plus a complete parameter schema cover safety and inputs. What remains unaddressed is operational context for a network-dependent multi-pillar audit, such as expected latency or behavior on a non-resolving domain.

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 coverage is 100% with only two parameters, both already documented with examples, so the schema carries the burden. The description adds only the framing that the domain should be the production domain, and says nothing about how brandName interacts with the trademark-screening pillar or what happens if it is omitted.

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 names a specific verb+resource (run a pre-launch audit on a production domain) and enumerates the three concrete pillars: brand/trademark screening, email deliverability (SPF/DKIM/DMARC/DNSBL), and AI search readiness (robots.txt, /llms.txt, JSON-LD). It also states the output artifact, a 0-100 Launch Scorecard with a remediation checklist, so an agent can tell exactly what this produces versus the single-pillar siblings.

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?

It gives an explicit trigger ('preparing a domain for launch or diagnosing overall technical growth readiness') and an explicit alternative plus the condition that selects it ('use the specialized single-pillar tools when iterating on just one area'). Nothing about tool selection 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.

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.