Skip to main content
Glama
kienpt91
by kienpt91

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
seo_free_auditA

Run SEOBolt's free anonymous audit for a public domain (sends the domain to seobolt.app). Returns an overall score, seo and llm sub-scores, and prioritized recommendations with how-to-fix text. Use it first for a broad overview of a site's technical SEO and AI-search readiness, then drill down with seo_check. Rate limit: anonymous, about 5 audits per 5 minutes per IP; on a rate-limit error stop and tell the user instead of retrying.

seo_checkA

Run ONE focused SEOBolt checker against a public domain or page (sends the target to seobolt.app). Use after seo_free_audit points at an area, or when the user asks about one specific thing (llms.txt, robots, sitemap, meta tags, structured data...). Input: tool plus target. Domain checkers want a domain; page checkers want a page URL. Returns verdict, pass/warn/fail counts and per-check detail with fixes. Rate limit: anonymous, roughly 3-10 calls per 5 minutes per IP depending on the checker. On a rate-limit error stop and tell the user; do not loop. Checkers:

  • llms-txt-checker (domain): Is there a valid /llms.txt (and optional llms-full.txt)?

  • ai-crawler-access-checker (domain): Does robots.txt let AI search and user-request crawlers reach the site?

  • chatgpt-visibility-checker (domain): Can the crawlers behind the most widely used chat assistant reach the site, plus on-page signals for being cited?

  • ai-citation-readiness-checker (url): Does a page carry the signals answer engines use to quote it (12 signals)?

  • redirect-checker (url): Follow the redirect chain of a URL and flag loops, long chains, http->https.

  • indexability-checker (url): Can search engines index the page (status, noindex, X-Robots-Tag, canonical)?

  • sitemap-checker (domain): Find and validate the XML sitemap.

  • structured-data-checker (url): Find and validate JSON-LD structured data on a page.

  • heading-structure-checker (url): Check H1 count and heading hierarchy on a page.

  • broken-link-checker (url): Check links found in the page's served HTML for broken or redirecting targets.

  • meta-tag-checker (url): Title, description, canonical, Open Graph and Twitter tags with length checks.

  • robots-txt-tester (domain): Fetch robots.txt and test whether named bots may crawl given paths (optional bots and paths).

mrr_leaderboardA

List startups on the ShowMRR public leaderboard ranked by monthly recurring revenue (queries showmrr.com). Optional category filter. Money is returned in cents plus currency. Each row says whether its figure is verified; 'NOT verified' figures must never be presented as verified revenue. Use mrr_stats to see categories first.

mrr_searchA

Search ShowMRR by startup name or keyword (sends the query to showmrr.com). Use it to look up a company's listed MRR when a founder or document claims a revenue number. No match only means the company is not listed, not that the claim is false. Results state whether each figure is verified.

mrr_statsA

Aggregate ShowMRR numbers: listing counts, verified count, total listed MRR and per-category totals (queries showmrr.com). Use it to get valid category slugs for mrr_leaderboard or the size of the dataset before drawing conclusions. The total includes unverified figures.

mrr_startupA

Fetch one ShowMRR startup by numeric id or slug (queries showmrr.com): MRR in cents plus currency, verification flag, revenue-as-of date, and for unclaimed listings the public page the figure was read from. Use it to check a specific company after mrr_search finds its slug. Never present a 'NOT verified' figure as verified revenue.

email_auth_checkA

Check a sending domain's SPF, DMARC, DKIM and MX records with DNS lookups made from this machine (no third-party API is called; queries go through your resolver to the domain's DNS servers, and include/redirect domains named in its SPF record are looked up too, up to 25 queries). Use it when mail lands in spam, before launching a sending domain, or to produce exact DNS fixes. Pass dkimSelectors (the s= value from a real message's DKIM-Signature header) for a definitive DKIM answer; without them only common selectors are probed, which cannot prove DKIM is absent. No rate limit beyond your resolver's.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation4/5

Each of the three domains (SEO, MRR lookup, email auth) is clearly separated, and the descriptions explicitly define the relationship between seo_free_audit (broad overview) and seo_check (focused drill-down), as well as mrr_search (find by name) → mrr_startup (fetch by slug/id). The main residual ambiguity is within seo_check, where 12 underlying checkers are folded into one tool with an opaque `tool` parameter, which an agent must parse rather than select between tools.

Naming Consistency5/5

All names are snake_case with consistent domain-prefix namespacing (seo_*, mrr_*, email_*) followed by a clear noun/verb, e.g. seo_free_audit, mrr_leaderboard, mrr_startup. The convention makes grouping and prediction of tool families obvious.

Tool Count5/5

Seven tools across three domains is well-scoped for a founder toolkit, and the decision to collapse 12 SEO sub-checkers into a single parameterized seo_check tool actively avoids tool explosion. Every tool earns its place with no filler.

Completeness4/5

The surface covers the read-only lifecycle well: SEO broad audit + focused checks, MRR search/leaderboard/stats/detail, and DNS-based email auth, with sensible handoffs between them. Minor gaps exist (no batch/multi-domain or cross-domain correlation, no historical comparison), but these are workarounds rather than blockers.

Maintenance

ActivityMaintained
ResponsivenessNo issues