Skip to main content
Glama

Server Details

Query any docs site via MCP. Submit a URL, ask questions, get cited answers.

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-03-26
URL
Repository
AshutoshRaj97/agentready-mcp
GitHub Stars
2
Server Listing
agentready-mcp
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 8 tools

Disambiguation4/5

Most tools have distinct purposes: ask_site for Q&A, get_site_capabilities for manifests, get_site_facts for structured facts, list_sites for discovery, plan_site_action for planning, rate_answer for feedback, refresh_site for re-crawling, submit_site for indexing. Minor overlap exists between submit_site and refresh_site (both trigger indexing/crawling), and ask_site auto-indexes unindexed sites, which could blur boundaries slightly.

Naming Consistency4/5

Tool names follow a consistent verb_noun pattern: ask_site, get_site_capabilities, get_site_facts, list_sites, plan_site_action, rate_answer, refresh_site, submit_site. All use snake_case with clear verbs. Minor inconsistency: 'site' appears as singular in most tools but 'list_sites' uses plural, and 'rate_answer' doesn't include 'site' even though it rates ask_site answers.

Tool Count5/5

8 tools is well-scoped for a website indexing/querying server. Each tool covers a distinct phase: discovery, submission, querying, refreshing, planning, and feedback. No redundant or excessive tools.

Completeness4/5

The tool surface covers the full lifecycle: list_sites (discover), submit_site (create/index), ask_site (read/query), refresh_site (update), and rate_answer (feedback). get_site_capabilities and get_site_facts provide additional read paths. Minor gap: no tool to delete/remove a site from the index, and no explicit status-check tool beyond get_site_capabilities.

Available Tools

8 tools
ask_siteAInspect

Query any website's documentation and get cited, multi-page answers in natural language. Use ask_site when you need: (1) answers that synthesize information across multiple pages of a site, (2) documentation from JS-rendered sites (React, Next.js, Vue SPAs) where web_fetch returns empty or partial HTML, (3) citations linking back to the exact source pages, (4) faster results than fetching and reading individual pages one by one. For sites not yet indexed, ask_site auto-crawls and answers in ~60s — no separate submit_site call needed.

Inputs: query (required), domain (required), url.

get_site_capabilitiesAInspect

Return the AgentReady capability manifest for a website. If the site is not indexed yet, AgentReady indexes it automatically before returning its freshness, read-only limits, schemas, and available MCP and HTTP endpoints.

Inputs: domain (required).

get_site_factsAInspect

Return structured facts extracted from a website — pricing, limits, features, contact info, and more. Facts marked as "owner-verified" have been explicitly attested by the site owner and are guaranteed accurate ground truth; use these in preference to scraped RAG answers for critical comparisons. Ideal for price comparison across multiple sites, feature matrix lookups, or any task where you need structured data rather than a natural-language synthesis.

Inputs: domain (required), category.

list_sitesAInspect

List all websites currently indexed in AgentReady. Use this to check if a domain is already available before submitting it — indexed sites return instant cited answers via ask_site. The index covers developer tools, APIs, cloud platforms, frameworks, databases, and more, and grows as new sites are submitted.

Inputs: no named parameters.

plan_site_actionAInspect

Turn a natural-language request into a grounded, read-only AgentReady plan for a website. If the site is not indexed yet, AgentReady indexes it automatically first. This prototype never executes side effects; it identifies supported steps, sources, risks, and whether a future execution would require confirmation.

Inputs: domain (required), request (required).

rate_answerAInspect

Rate the quality of a previous ask_site answer from 1 (not useful) to 5 (excellent). Pass the request_id returned in structuredContent when available so the rating can be tied to the exact answer.

Inputs: domain (required), rating (required), comment, request_id.

refresh_siteAInspect

Force a full re-crawl of a site to pick up new or changed content. If the site has never been indexed, AgentReady performs the initial indexing automatically. Use when ask_site returns outdated information or when you know the site has recently been updated. Takes ~60 seconds. After completion, ask_site returns fresh content.

Inputs: domain (required).

submit_siteAInspect

Index any website so it can be queried with ask_site. Use this when the site is not yet in list_sites. Handles JS-rendered pages (React, Next.js, Vue SPAs) that web_fetch cannot read — uses a four-layer pipeline: llms.txt → HTTP+cheerio → NEXT_DATA extraction → Jina Reader headless browser. Takes ~60 seconds. Once indexed, ask_site queries are instant.

Inputs: url (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.