Domain DA-PA Checker: Domain authority score & page authority score, spam score, backlink count.
Scored across 1 tool
With only one tool available, there is no possibility of confusion between tools. The agent will know exactly which tool to call since there is only one.
'get_v1' appears to be a generic versioned API endpoint name rather than a meaningful tool name for the domain. While there are no inconsistencies with only one tool, the name reveals nothing about its purpose, making it especially unhelpful within a broader tool ecosystem.
A single tool for a domain authority check is on the thin side, even for a narrow niche. The scope feels slightly underdelivered, and an agent would likely benefit from at least one additional tool (e.g., batch checking) to justify its existence as a separate server.
The single tool aggregates the core metrics (DA, PA, spam score, backlinks) into one call, covering the primary workflow of a domain authority checker. Only minor features like historical tracking or bulk lookup are missing, which feels like an acceptable gap for this narrow scope.
Target, Domain Authority Score, Page Authority Score, Spam Score, Total Backlinks Billing per call: 1 Credits.
| Name | Required | Description | Default |
|---|---|---|---|
| target | No |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full disclosure burden. It does disclose a per-call credit cost and implies a read-only metrics lookup, but it lacks authentication context, required-parameter expectations, failure behavior, or any clarification of return format.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is short and includes relevant information, but the metric list and billing clause run together without clear punctuation ('Total Backlinks Billing per call: 1 Credits'). This hurts readability even though the overall length is appropriate.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
There is no output schema and no annotations, so the description is the primary context. It lists the expected metrics and cost but does not specify the return contract, required input semantics, or boundary conditions, leaving significant gaps for an agent trying to invoke and parse results correctly.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
There is one parameter and the schema description coverage is 0%. The description only repeats 'Target' and does not state how the target should be formatted, whether it is required, or what value forms are accepted beyond what the schema title already shows.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description lists domain metrics (Domain Authority Score, Page Authority Score, Spam Score, Total Backlinks) and a target, so the intended purpose can be inferred. However, there is no verb or action statement like 'returns' or 'retrieves', leaving the tool's exact purpose ambiguous.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
There is no guidance on when to use this tool or how it compares to alternatives. The only extra guidance-like content is 'Billing per call: 1 Credits', which is a cost warning rather than a usage instruction.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
get_v1Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity – fastest for official registry listings. For a namespace such as io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such as io.github.acme/server also needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.
HTTP challenge – works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at /.well-known/glama.json on the same origin as the connector, then choose Check HTTP challenge.
DNS challenge – works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Website authority and AI visibility tools for DR, TrueDR, keywords, backlinks, and partnerships.
Screen expired domains: availability, drop stage, history, brandability, trademark risk.
DNS lookups, health reports, SSL certs, security scans, GEO scoring, uptime checks
Free SEO tools + the Spook SEO autopilot: analyze domains, generate and publish SEO articles.
