Skip to main content
Glama

pageaudit__smpeek

Web page intelligence for agents: audit pages, check SEO metadata, preflight URL liveness, monitor pages for changes, vet x402 sellers, and compare perp funding rates across Binance/OKX/Bybit/Gate. $0.01/call USDC on Base; free real previews. Price: $0.01 per call in USDC on Base (eip155:8453), paid with x402 in params._meta["x402/payment"]. HTTP: GET https://api.firstmention.uk/s/pageaudit/smpeek

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "pageaudit__smpeek"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added
  2. Removed
  3. Added
  4. Removed
  5. Added

TDQS

C2.4/5.0
Behavior3/5

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

With no annotations, the description must carry the full behavioral load, and it does supply genuinely useful context: cost ($0.01/call in USDC on Base, eip155:8453), the x402 payment location (params._meta["x402/payment"]), free previews, and the HTTP endpoint. What it omits is what a call returns, whether url is optional in practice, or what happens when url is absent — significant gaps for a multi-mode tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness2/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Pricing is stated twice — once as '$0.01/call USDC on Base; free real previews' and again as 'Price: $0.01 per call in USDC on Base (eip155:8453)' — which is pure waste in a three-sentence description. The capability list is front-loaded reasonably, but the duplication and the unprioritized six-item menu hurt it.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with one undocumented optional parameter, no annotations, and no output schema, the description should explain the default behavior when url is omitted and roughly what comes back. Instead it spends its words on a duplicated price and a capability list, leaving the agent unable to predict the result of a call.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0% for the single url parameter, so the description must compensate and does not: it never states that url is the target page, that it is optional per the schema, or how url interacts with the funding/seller-check modes that arguably need a different input. The only parameter is left entirely unexplained.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose3/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names concrete resources and verbs (audit pages, check SEO metadata, preflight URL liveness, vet x402 sellers, compare funding rates), so it is more than a tautology. However, it conflates six unrelated capabilities into one tool without saying which of them a single invocation performs, so an agent cannot form a precise expectation of what this tool actually does.

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

Usage Guidelines2/5

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

There is no when-to-use guidance and no exclusions. The sibling list contains pageaudit__audit, pageaudit__peek, pageaudit__preflight, pageaudit__watch, pageaudit__sellercheck, and pageaudit__funding, which appear to map to the very capabilities this description lists, yet the description never routes the agent to any of them or explains why smpeek should be chosen instead.

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