Skip to main content
Glama
Sign In

Landfall

by io.github.landfall-audit
OverviewDiscussionsAdmin

Preview a landing page audit (free)

preview_landing_page
Read-onlyIdempotent

Free quick check of a landing page: ready / fix_first / not_ready verdict, 0-100 score, issue counts and the most important blocker. Limited per hour. Use audit_landing_page for the evidence and fixes.

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

Input Schema

NameRequiredDescriptionDefault
urlYesPublic http(s) URL of the landing page, e.g. https://example.com/offer

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint, so the safety profile is covered. The description adds real value beyond them: the rate limit ('Limited per hour') and the shape of the result (verdict tiers, score range, issue counts, top blocker). It does not say what happens on an unreachable URL or how the limit is enforced.

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 tight sentences, front-loaded with what the tool returns before the routing hint and the rate-limit caveat. No filler and nothing redundant with the schema.

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?

There is no output schema, so the description correctly spends words summarizing the return payload (verdict, score, counts, blocker) plus the throttling constraint. Combined with full schema coverage and read-only annotations, an agent has everything needed to call this correctly.

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?

The single url parameter is fully documented in the schema (100% coverage, with format example), so the schema carries the parameter burden. The description adds no additional syntax, constraint, or example for url; baseline 3 applies when schema coverage is high.

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 (preview/quick check), resource (landing page), and the concrete payload the caller gets: verdict, 0-100 score, issue counts, top blocker. It clearly distinguishes itself from audit_landing_page as the lightweight version.

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?

Explicitly names the alternative (audit_landing_page) and the condition that selects it ('for the evidence and fixes'), so an agent knows this tool is the fast triage call and the sibling is the deep-dive. It also flags the per-hour limit, which shapes call-frequency decisions.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Landfall toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources