Skip to main content
Glama

Agent402.Tools: pay-per-call web tools

by io.github.MikeyPetrillo

Search the Agent402 tool catalog

catalog.search
Read-onlyIdempotent

BROWSE the long catalog behind the flagship set: keyword search over Agent402's 500+ pay-per-call tools (exact count 579). Start with the listed flagships for search/answer/news/render/data/transcribe/memory; use this when you need a long-tail slug. Counterpart catalog.find resolves a task to ONE ready-to-run pick - search explores, find decides. 165 pure-CPU tools run free here (proof-of-work); the rest are payable right here over MPP (credential in _meta - mppx McpClient pays automatically) or via npx agent402-mcp with a wallet. Also an OpenAI-compatible LLM gateway at https://agent402.tools/v1 (flat per-call; wallet = account). Returns { results, workflows }; run one with catalog.call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMax results (default 10)
queryYesWhat you need, e.g. "search the web for x402", "answer a question with citations", "decode JWT"

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNoShown when the match is weak - points at demand.request
usageNo
messageNoPresent when nothing matched
resultsYesMatching catalog tools
workflowsNoMatching skill-pack workflows
workflowsUsageNo

TDQS

A4.4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive behavior. The description adds meaningful context about exact catalog size, free vs payable tools, MPP credential handling, an LLM gateway, and the return shape, going well beyond the structured annotations without contradicting them.

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?

Dense and information-rich, with the core purpose and usage front-loaded. Some extra topics (LLM gateway, exact payment details) go beyond the bare minimum but each adds practical context for an agent deciding whether and how to call this tool.

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?

Covers the tool's purpose, relationship to siblings, payment/auth options, response format, and next step (catalog.call). With an output schema present and annotations covering safety, nothing critical is missing for an agent to use 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 covers both parameters fully (query with examples, limit with default), so baseline is 3. Description adds the 'long-tail slug' use case and return shape but does not add new parameter-level semantics beyond what schema already provides.

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?

Description explicitly states this is a keyword search over the long catalog, distinct from the flagship set, and contrasts itself with catalog.find. The verb 'BROWSE' plus the resource (catalog) and the search nature make the tool's role unmistakable.

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?

Provides clear when-to-use guidance: start with flagships, use this for long-tail slugs, and use catalog.find when a single decided pick is needed. Also explains how to invoke returned workflows via catalog.call, making the usage path complete.

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

All Agent402.Tools: pay-per-call web tools toolsInspect
Try in Browser
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0
Disambiguation4/5

Tools are grouped by clear domain prefixes (web, memory, catalog, market) and mostly have distinct behaviors. web.search and web.news overlap somewhat as both return ranked live results, and catalog.find vs catalog.search require careful reading, but the descriptions do enough to disambiguate them.

Naming Consistency5/5

Every tool follows the same dotted domain.action pattern with lowercase snake_case, e.g. web.search, memory.read, catalog.find. This is highly predictable and lets an agent infer the general behavior of an unfamiliar tool from its name alone.

Tool Count4/5

Fifteen tools is at the upper edge of the well-scoped range, but each represents a distinct capability or meta-function like payment info and catalog discovery. The count feels reasonable for a pay-per-call marketplace front-end, though a few auxiliary tools (sellers.list, demand.request) are slightly peripheral.

Completeness4/5

The flagship set covers the main workflows: web search/news/answer, rendering, transcription, market quotes, memory read/write, and catalog lookup. Some referenced tools like extract and screenshot are not included as first-class tools, but the catalog.call/search/find trio and demand.request make those gaps addressable rather than dead ends.

Resources