Skip to main content
Glama

LeadSail — Software Growth Engine

Audit a product page's buyer-readiness

audit_store
Read-only

Run a free readiness audit of a software product page: fetch the page and check the signals that decide whether visitors become buyers (lead capture, CTA, contact info, trust signals, chat, social, mobile, SEO basics, HTTPS). Returns a readiness score and top issues with evidence.

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": {
      "url": "<url>"
    },
    "name": "audit_store"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlYesThe software product page URL to audit, e.g. https://example.com/product

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / url / description
      Previous value: -"The store URL to audit, e.g. https://example-store.com"New value: +"The software product page URL to audit, e.g. https://example.com/product"
  2. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already declare readOnlyHint and openWorldHint, and the description adds meaningful context beyond them: the tool fetches the live page over the network, is free, and returns a readiness score plus top issues with evidence. It omits failure behavior for unreachable or non-HTML pages and any rate limits, which keeps it from a 5.

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?

Two sentences, front-loaded with the action and result, with the signal list compressed into one parenthetical. The enumeration is dense but each item earns its place by telling the agent what evidence the audit covers.

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 single-parameter, read-only tool with annotations covering safety and open-world access, the description covers input intent, what is inspected, and what comes back despite there being no output schema. Error and pagination behavior are the only notable omissions.

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% for the single url parameter, including an example format, so the schema carries the load. The description adds no constraint or format detail about the URL beyond what the schema states, making 3 the appropriate baseline.

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?

Specific verb ("Run a free readiness audit") plus resource ("a software product page") and an enumerated set of checked signals, so the agent knows exactly what the tool does. It does not explicitly differentiate itself from siblings like radar_scan or about_leadsail, 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?

Usage is implied by the framing (audit a product page's buyer-readiness) and the word "free" signals no cost barrier, but there is no explicit when-to-use/when-not guidance or named alternative for adjacent tasks.

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