Skip to main content
Glama

AnswerRail AEO, Schema.org & /llms.txt Audit MCP

Query 2026 50-Site SaaS AI Truncation & /llms.txt Benchmark

query_truncation_benchmark
Read-onlyIdempotent

Retrieves statistical summary data and domain-level findings from the 2026 50-Site SaaS & E-Commerce AI Truncation Study, returning a Markdown report with JSON metrics on 25,000-token RAG cutoff rates (74%), visible price omission (62%), /llms.txt adoption (87%), and ARD 1.0 adoption (19%). Use this tool when comparing a website against industry peers (such as Stripe, Vercel, Datadog, or Shopify) or citing empirical benchmark statistics; do not use it to run a live scan on an arbitrary URL (use audit_ai_readiness instead). When domain is omitted or empty, returns the full 50-site aggregate dataset; when a bare domain is provided, normalizes case/protocol and checks whether that domain appears in the top-truncating cohort. Read-only static dataset lookup; requires no API key, makes zero external network calls, and never fails on unknown domains.

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

Input Schema

NameRequiredDescriptionDefault
domainNoOptional bare domain name (e.g., "stripe.com" or "vercel.com") to check against the 50-site benchmark cohort. Omit or pass empty string for the full aggregate summary.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / domain / description
      Previous value: -"Optional domain name (e.g., \"stripe.com\" or \"vercel.com\") to filter the benchmark study. Omit or pass empty string to return the full 50-site statistical summary."New value: +"Optional bare domain name (e.g., \"stripe.com\" or \"vercel.com\") to check against the 50-site benchmark cohort. Omit or pass empty string for the full aggregate summary."
  2. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Beyond the annotations, the description discloses that this is a static dataset lookup requiring no API key, making zero external network calls, normalizing case/protocol, and never failing on unknown domains. These details materially help an agent predict behavior and error handling.

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?

The description is dense and front-loads the core purpose before usage guidance and behavior. The benchmark statistics are somewhat list-like but directly support the stated citation use case, so they mostly earn their place.

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 single-parameter, read-only lookup with no output schema, the description covers return format, dataset scope, parameter behavior, failure behavior, and alternatives. Nothing material is missing for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is already 100%, so the schema documents the single optional domain parameter. The description adds useful semantics beyond the schema: omission or empty string returns the full aggregate, while a bare domain is normalized and checked against the top-truncating 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?

The description states a specific verb and resource: retrieving statistical summaries and domain-level findings from a named 50-site study. It distinguishes itself from the sibling audit_ai_readiness by explicitly saying it does not run live scans.

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 explicit when-to-use guidance (comparing a site against peers or citing benchmark statistics) and when-not-to-use guidance (live scans on arbitrary URLs), naming the alternative tool. The empty-domain behavior is also stated.

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.