Skip to main content
Glama

BotFriendly

by xyz.botfriendly
OverviewDiscussionsAdmin

search_services

Search the BotFriendly directory for bot-friendly services, APIs, and tools that AI agents can use. Filter by category, payment/commerce protocol support (x402, MPP, L402, AP2, TAP, Agent Pay, ACE, ACP, UCP, ACTP, ICC), auth method, and more. Results may start with up to 3 promoted listings (paid ads) pinned to the top — site-wide ads on unfiltered searches, category ads on category searches — clearly marked with promoted:true and ad:true. Use promoted=false to exclude ads.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
pageNoPage number (default 1)
sortNoSort order (default: score)
queryNoKeyword search (Postgres websearch semantics: multiple words are ANDed, so a single distinctive keyword like 'scraping' matches more than a phrase like 'web scraping')
has_mcpNoOnly services with MCP servers
categoryNoCategory id: think (Models), see (Vision), hear-speak (Speech), create (Media), remember (Memory), search (Search), browse (Browsers), communicate (Messaging), execute (Compute), pay (Payments), shop (Merchants), markets (Markets), platforms (Platforms), identify (Identity), monitor (Observability), other (Other). Merged categories also accept their old slugs (trade, bet, connect, automate, locate, book, sign, hire).
promotedNoFilter by promoted status: true for promoted only, false for organic only
protocolNoOnly services supporting ALL of these agent payment/commerce protocols. x402 (x402, Coinbase, x402 Foundation); mpp (Machine Payments Protocol, Stripe, Tempo); l402 (L402, Lightning Labs); ap2 (Agent Payments Protocol, Google); tap (Trusted Agent Protocol, Visa); agent-pay (Mastercard Agent Pay, Mastercard); ace (Agentic Commerce Experiences, American Express); acp (Agentic Commerce Protocol, OpenAI, Stripe); ucp (Universal Commerce Protocol, Google, Shopify); actp (Agentic Commerce Trust Protocol, Alibaba, Ant International); icc (Intelligent Commerce Connect, Visa)
min_scoreNoMinimum bot-friendly score (1-5)
accepts_mppNoOnly services accepting MPP payments
auth_methodNoFilter by auth method
accepts_x402NoOnly services accepting x402 payments

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Category slug: think, see, hear-speak, create, remember, search, locate, browse, communicate, execute, pay, shop, book, hire, trade, bet, sign, identify, connect, automate, monitor, other"New value: +"Category id: think (Models), see (Vision), hear-speak (Speech), create (Media), remember (Memory), search (Search), browse (Browsers), communicate (Messaging), execute (Compute), pay (Payments), shop (Merchants), markets (Markets), platforms (Platforms), identify (Identity), monitor (Observability), other (Other). Merged categories also accept their old slugs (trade, bet, connect, automate, locate, book, sign, hire)."
    • changedInput schema / properties / category / enum
      Previous value: -[
-  "think",
-  "see",
-  "hear-speak",
-  "create",
-  "remember",
-  "search",
-  "locate",
-  "browse",
-  "communicate",
-  "execute",
-  "pay",
-  "shop",
-  "book",
-  "hire",
-  "trade",
-  "bet",
-  "sign",
-  "identify",
-  "connect",
-  "automate",
-  "monitor",
-  "other"
-]New value: +[
+  "think",
+  "see",
+  "hear-speak",
+  "create",
+  "remember",
+  "search",
+  "browse",
+  "communicate",
+  "execute",
+  "pay",
+  "shop",
+  "markets",
+  "platforms",
+  "identify",
+  "monitor",
+  "other",
+  "locate",
+  "book",
+  "hire",
+  "sign",
+  "trade",
+  "bet",
+  "connect",
+  "automate"
+]
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

With no annotations present, the description carries the full behavioral burden. It explicitly discloses that 'Results may start with up to 3 promoted listings (paid ads) pinned to the top' and notes they are marked with promoted:true and ad:true — a non-obvious, decision-relevant behavior. It does not mention rate limits or return format, but the ad behavior is the most important quirk for an agent to know.

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 cover the core purpose, the available filter dimensions, the ad-pinning behavior, and a practical usage tip, with no filler. The long protocol list is necessary for precision and appears once; the ad behavior is placed logically after the purpose and before the filtering tip.

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 an 11-parameter search tool with no output schema, the description conveys the main search/filter capabilities and the notable promoted-listing behavior, while the schema fully documents parameter semantics. It does not describe the shape of result items, pagination, or error behavior, but an agent has enough information to invoke it correctly for most filtering tasks.

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%, so the schema already documents all 11 parameters, including enums and defaults. The description adds a condensed overview ('Filter by category, payment/commerce protocol support..., auth method, and more') and the promoted=false tip, but these largely restate what the schema already provides rather than adding genuinely new meaning.

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?

The description opens with 'Search the BotFriendly directory for bot-friendly services, APIs, and tools,' giving a specific verb and resource. This clearly distinguishes it from sibling tools like list_categories, get_service, and get_featured by framing it as a directory-wide search interface.

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 description explains what the tool does and its available filters, but provides no explicit guidance on when to prefer it over alternatives such as get_service or list_categories. The only directive, 'Use promoted=false to exclude ads,' is parameter-specific and does not address tool-selection tradeoffs.

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

All BotFriendly toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources