Skip to main content
Glama

Get Site Profile

alterlab_site_profile
Read-onlyIdempotent

Look up what AlterLab has measured about a domain across many customers' recent unauthenticated scrapes: success_rate, typical_tier, typical_cost_microcents and typical_cost_usd, median_latency_ms, antibot_vendor, and common_failures (code, share, retryable), each with its sample size in field_samples. Use before scraping an unfamiliar site to budget credits and set expectations; it is read-only and informational, AlterLab still chooses the tier, proxy and pace for every request. A field with too few measured samples is omitted, never estimated. An unknown or unpublished domain returns known: false and the free estimate path (alterlab_estimate_cost). Free and keyless, no credits are spent, and a call never scrapes the site.

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

Input Schema

NameRequiredDescriptionDefault
domainYesHostname only, e.g. example.com (no scheme, path or query)

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A4.2/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 the description adds what annotations cannot: free and keyless, no credits spent, and a call never scrapes the site. It also discloses a data-quality behavior that matters for interpretation — fields with too few samples are omitted rather than estimated, and unknown domains return known: false. Return-shape details are partly covered by the field enumeration.

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?

Front-loaded with purpose, then usage, then behavioral caveats, with each sentence carrying distinct information. The latency/cost/antibot field list is long but functional; minor tightening is possible around the cost_usd/microcents duplication.

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?

No output schema exists, so the description must describe return values — it enumerates the fields including field_samples, common_failures sub-fields and the known:false sentinel, which is largely sufficient for calling and interpreting the tool. What remains unaddressed are details like whether samples are cached or how current the measurements are.

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% and the single domain parameter is already documented with a hostname example (no scheme, path or query), so the schema does the heavy lifting. The description adds no further meaning about the domain argument itself, which fits the baseline for full schema coverage.

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?

Opens with a specific verb and resource ("Look up what AlterLab has measured about a domain") and enumerates the exact fields returned, so an agent knows this is a market-measurement lookup rather than a scraper or a cost calculator. It also distinguishes itself from alterlab_estimate_cost by describing that tool as the fallback path for unknown domains.

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

Usage Guidelines5/5

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

States an explicit trigger ("Use before scraping an unfamiliar site to budget credits and set expectations") and names the alternative tool (alterlab_estimate_cost) for the unknown-domain case. It also rules out misuse by clarifying that AlterLab still chooses tier, proxy and pace, so this profile does not configure requests.

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.