Skip to main content
Glama

SouthPow crypto & market data

buy_search

Paid. Web search for AI agents: query in, ranked live web results out (title, url, published date, author). $0.006 USDC on Base per search. No account, no API key. Failed searches are not charged. URL https://southpow.media/v1/search.

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": {
      "q": "<q>"
    },
    "name": "buy_search"
  }
}

Input Schema

NameRequiredDescriptionDefault
nNoNumber of results, 1-10 (default 5)
qYesSearch query

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.7/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does real work: it discloses a $0.006 USDC-on-Base charge per search, that no account or API key is needed, and that failed searches are not charged. It stops short of describing the payment mechanism (how USDC is transferred without an account), rate limits, or what constitutes a failure.

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?

It is telegraphed well: "Paid" first as the key constraint, then what it does, what comes back, price, and payment terms. The trailing raw endpoint URL is arguably noise for an MCP tool, which is the only wasted token.

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 two-parameter paid search tool with no output schema, the description supplies the return fields and the billing/failure behavior an agent needs to decide whether to spend. Only the actual payment flow is left unexplained, which is a minor gap given everything else covered.

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 both parameters, so the schema already documents q and n (1-10, default 5). The description confirms "query in" but adds no syntax, format, or tuning guidance beyond the schema, which is the expected baseline here.

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?

"Web search for AI agents: query in, ranked live web results out (title, url, published date, author)" names a concrete verb, resource, and return shape, so the agent knows exactly what it gets. It does not explicitly distinguish itself from sibling search_facts or the other buy_* feeds, which keeps it 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?

The word "Paid" plus the per-search price implies this is the option for live, open-web results and that a cost is involved, which is implicit routing guidance. However, it never says when to prefer it over search_facts or buy_hn, and never states any exclusion or precondition beyond the implicit ability to pay.

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