Skip to main content
Glama

ASO Studio Live Domain Audit & Self-Serve ASO Pack

Find a SaaS teardown

lookup_domain_aso_teardown
Read-onlyIdempotent

Search 2,458 audited SaaS domains by domain or brand. Returns up to 12 teardown links; an empty list means no indexed match.

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": {
      "query": "<query>"
    },
    "name": "lookup_domain_aso_teardown"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesDomain or brand keyword, for example helicone.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so safety needs no restating. The description still earns credit by disclosing corpus size (2,458 domains), the result cap (up to 12 links) and the meaning of an empty list, which are not derivable from the annotations.

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 corpus scope front-loaded and the return contract in the second sentence. Nothing is padded or repeated.

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?

The tool is a one-parameter lookup with full annotation coverage and no output schema, and the description still covers what comes back (up to 12 teardown links) plus the empty-result meaning. An agent has everything needed to call it and interpret the response.

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?

With a single parameter at 100% schema description coverage, the schema already states "Domain or brand keyword, for example helicone." The description's "by domain or brand" largely repeats that, adding no format, matching, or fuzzy-vs-exact semantics beyond it.

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 pairs a specific verb and resource ("Search ... audited SaaS domains") with a concrete scope ("2,458 audited SaaS domains", "by domain or brand"), so the agent knows exactly what it retrieves. It does not explicitly contrast itself with siblings such as probe_domain_aso_score or compare_domain_aso_scores, so it stops short of a 5.

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?

"Search ... by domain or brand" implies the lookup use case, and the empty-list note hints at a pre-check role, but there is no explicit statement of when to pick this over probe_domain_aso_score or the router. Usage is inferable rather than 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.

Resources