Skip to main content
Glama

ADS Beast

seo_domain_authority_audit

Read-only

A 40-criteria audit of domain authority: citation, identity, trust and eminence. AI: 1 AI request.

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

Input Schema

NameRequiredDescriptionDefault
domainYesDomain without scheme.
client_idNo
site_typeNoType of site, for weighting.saas

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.1/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so safety is covered. The description adds useful behavioral context by stating it runs 40 criteria and consumes 1 AI request, which tells the agent about scope and cost. It does not describe output, auth, or rate constraints, so it is adequate but not rich.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two short sentences, with the core audit scope front-loaded and the AI-cost note kept terse. There is no redundant filler.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The tool is a read-only audit with a clear purpose, and the annotations plus schema cover safety and required input. However, with no output schema, the description does not explain what the 40-criteria audit returns or how site_type affects weighting, leaving gaps for an agent interpreting results. It is minimally adequate.

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

Parameters2/5

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

Schema coverage is 67%: domain and site_type have descriptions, but client_id is undocumented. The description does not mention any of the three parameters or clarify site_type weighting or client_id usage, so it adds essentially no meaning beyond the schema. The moderate coverage and undocumented optional parameter justify a low score.

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?

The description states a specific verb ('audit') and resource ('domain authority') and scopes it with 40 criteria across citation, identity, trust, and eminence. It does not name a sibling tool or explicitly say how it differs from related SEO audits, so it falls short of full sibling differentiation.

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

Usage Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance, and no alternative tool is named. The purpose implies it is for domain authority work, but an agent must infer selection from the name alone.

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.