Skip to main content
Glama

Agent402.Tools: pay-per-call web tools

by io.github.MikeyPetrillo

Resolve a task to the one best Agent402 tool

catalog.find
Read-onlyIdempotent

DECIDE, don't browse: resolve a plain-language task to the single best-matching Agent402 tool, returned call-ready - slug, price, input schema, and a worked example (its counterpart catalog.search returns a list of candidates to compare - search explores, find decides). Prefer this for anything outside the flagship list. Returns { task, results } with the top pick first; then run catalog.call with the chosen slug + params.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
taskYesWhat you want to do, e.g. "search the web for x402 adoption" or "convert miles to km"
limitNoMax results (default 5)

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
hintNo
taskYes
usageNo
matchesNoAlias of results on the stdio package
messageNo
resultsNoRanked matches; top pick first
workflowsNo
relatedSellersNo
workflowsUsageNo

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnly and non-destructive, so the description adds value by detailing the output structure ({ task, results }), the 'top pick first' ordering, and the call-ready artifacts (slug, price, schema, example). It does not contradict annotations.

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

Conciseness5/5

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

Three sentences each add distinct value: purpose, contrast with sibling, and next-step guidance. No filler, information is front-loaded with 'DECIDE, don't browse'.

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?

Given the output schema exists, the description adequately covers what the tool returns, when to use it, and the follow-up action. Contextual signals (siblings, annotations, schema) together make the tool fully understandable.

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%, so the baseline is 3. The description adds minimal parameter-specific meaning beyond the schema, only referring to 'plain-language task' which the schema already conveys with examples.

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 clearly states it resolves a plain-language task to the single best-matching tool, with a specific verb + resource. It explicitly contrasts with catalog.search, so sibling differentiation is strong.

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 explicit guidance: 'Prefer this for anything outside the flagship list' and names the alternative catalog.search for exploring candidates. Also instructs to use catalog.call after selection, making the call flow clear.

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