Skip to main content
Glama

AEO Auditor — AI Search & Agent Readiness Engine

get_domain_benchmark

Look up a domain AEO readiness benchmark score and 4-pillar breakdown, or query the industry leaderboard directory across SaaS, AI, FinTech, DevTools, and E-Commerce.

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

Input Schema

NameRequiredDescriptionDefault
domainNoOptional domain name to retrieve benchmark profile (e.g. "openai.com"). Omit to list top leaderboard domains.
categoryNoOptional industry category filter when listing leaderboard benchmarks (e.g. "ai", "fintech", "developer_tools", "saas", "ecommerce").

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional industry category filter when listing leaderboard benchmarks (e.g. \"AI & ML\", \"FinTech\", \"DevTools\", \"SaaS\")."New value: +"Optional industry category filter when listing leaderboard benchmarks (e.g. \"ai\", \"fintech\", \"developer_tools\", \"saas\", \"ecommerce\")."
  2. First observed

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations, the description must carry the behavioral load; 'look up' and 'query' imply a read-only, non-mutating operation, and it does disclose the shape of the result (score plus 4-pillar breakdown, or a leaderboard listing). It omits data freshness, coverage of the benchmark corpus, any auth/rate-limit constraints, and whether the leaderboard is paginated or capped.

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?

A single front-loaded sentence that pairs the two modes cleanly with 'or', with no filler. The vertical list at the end is slightly verbose but does useful work by signaling category breadth.

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 simple two-parameter, zero-required, read-only lookup with no output schema, the description covers both modes and the returned content well enough to call it correctly. Gaps are minor: no leaderboard size/pagination note and no explicit contrast with audit_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%, so both parameters are already documented with examples and the omit-to-list behavior. The description adds only marginal value by enumerating the industry verticals (SaaS, AI, FinTech, DevTools, E-Commerce), which loosely maps to the category values but does not add syntax or default behavior beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb ('look up'/'query') and resource ('domain AEO readiness benchmark score and 4-pillar breakdown' / 'industry leaderboard directory'), so the agent knows exactly what data comes back. It does not explicitly name or differentiate itself from the sibling audit_domain, leaving the benchmark-vs-audit distinction to inference.

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

Usage Guidelines3/5

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

The two operating modes are implied by 'or query the industry leaderboard directory', and the schema clarifies that omitting domain lists the leaderboard. However, there is no explicit when-to-use guidance and no statement about when to prefer this over audit_domain or the remediation siblings.

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.

Resources