Skip to main content
Glama

SouthPow crypto & market data

buy_audit_seo

Paid. On-page SEO audit of a URL: title, meta description, H1, canonical, alt text, word count, Open Graph, issue list and score. $0.05 USDC on Base or Solana. No account, no API key. Failed calls not charged. URL https://southpow.media/v1/audit/seo.

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

Input Schema

NameRequiredDescriptionDefault
urlYesWebsite URL or domain, e.g. https://example.com

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?

With no annotations supplied, the description carries the full burden and does well: it discloses that the call is paid, the exact price ($0.05 USDC), the accepted payment chains (Base or Solana), that no account or API key is required, and that failed calls are not charged. What it omits is any note on latency, rate limits, or what a partial/failed audit response looks like.

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?

The description is front-loaded with the key qualifier 'Paid.' and then the purpose, output contents, and payment terms in a compact sequence. It is dense but readable; the raw endpoint URL at the end is the only piece that could be trimmed as redundant for an agent that already has the tool binding.

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 one-parameter tool with no annotations and no output schema, the description compensates well by enumerating the returned fields and the payment mechanics. The main residual gap is the shape of the error/partial-result case, though 'failed calls not charged' partially covers it.

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?

There is a single parameter at 100% schema description coverage, so the schema already explains 'Website URL or domain, e.g. https://example.com'. The description adds no further syntax, normalization, or redirect-handling detail about the url argument, so baseline 3 applies.

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 and resource ('On-page SEO audit of a URL') and enumerates exactly what the audit returns: title, meta description, H1, canonical, alt text, word count, Open Graph, issue list and score. This is clearly separable from the sibling security audit and bundle tools without opening any schema.

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?

The scope ('on-page SEO') implies appropriate usage, and the payment prerequisites are spelled out, but the description never says when to choose this over buy_audit_security or buy_audit_bundle, nor does it state any exclusions or limits on what URLs are acceptable.

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