Skip to main content
Glama

ASO Studio Live Domain Audit & Self-Serve ASO Pack

Compare two domains

compare_domain_aso_scores
Read-onlyIdempotent

Compare two public domains using the free live ASO audit. Returns both scores, missing signals and score_delta (domain_a minus domain_b).

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_a": "<domain_a>",
      "domain_b": "<domain_b>"
    },
    "name": "compare_domain_aso_scores"
  }
}

Input Schema

NameRequiredDescriptionDefault
domain_aYesPublic domain, for example example.com; private hosts are rejected.
domain_bYesPublic domain, for example example.com; private hosts are rejected.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4/5.0
Behavior3/5

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds that results come from a free live audit and names the returned fields (both scores, missing signals, score_delta), which is useful given no output schema, but it says nothing about latency, failure modes for rejected private hosts, or whether the two domains must differ.

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?

Two short sentences, zero filler, with the action front-loaded and the return shape immediately after. Every clause carries information the agent can use.

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 two-parameter read-only tool with no output schema, the description covers purpose, mechanism and return values adequately. Minor gaps remain on error behavior for private or duplicate domains and on whether results are cached, but nothing essential for invoking it correctly is missing.

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 100%, so the baseline would be 3. The description earns an extra point by defining the sign convention of the derived value — "score_delta (domain_a minus domain_b)" — which tells the agent how parameter ordering affects the result, information not present in the schema.

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?

States a specific verb and resource ("Compare two public domains") plus the mechanism ("free live ASO audit") and even the outputs. An agent can distinguish this pairwise comparison from the single-domain sibling probe_domain_aso_score purely from the text.

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?

Usage is only implied: the word "Compare" and "two" signal the pairwise case, and "free live" hints at no-cost real-time evaluation. There is no explicit statement of when to prefer this over probe_domain_aso_score or lookup_domain_aso_teardown, and no exclusions or prerequisites.

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