Skip to main content
Glama

Search402

How to call the paid endpoints

how_to_pay

Exact URLs, prices and the x402 payment steps for full search and page extraction.

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

Input Schema

NameRequiredDescriptionDefault
qNoOptional query to build the search URL

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

B3.4/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the response content (URLs, prices, payment steps), which is the key behavioral fact for a help/reference tool, but it never states that calling it performs no payment or side effects, nor whether the returned prices/URLs are static or account-specific.

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?

One tight sentence with the substantive payload front-loaded and no filler. It reads as a noun fragment rather than a complete sentence, which slightly reduces clarity but wastes no words.

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

Completeness3/5

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

For a simple one-optional-param tool with no output schema, the description covers what content comes back but omits the q parameter's effect and any statement that this is informational only. Adequate to select the tool, thin on how to invoke it 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?

Schema description coverage is 100%, and the single optional parameter q is documented in the schema as building the search URL. The description says nothing about q or how the returned URLs vary with it, so it adds no meaning beyond the schema — baseline 3 applies.

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?

The description names the concrete payload — exact URLs, prices, and x402 payment steps — and scopes it to full search and page extraction, which separates it from index_status and search_preview. It lacks an explicit verb (e.g., 'returns' or 'explains'), so an agent must infer from the name/title that this is a reference tool rather than something that performs payment.

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 phrase 'for full search and page extraction' implies the situation in which to call it, but there is no explicit when-to-use or when-not-to-use statement, and no mention of how it relates to search_preview or the paid flow. Usage is inferable rather than stated.

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