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).
no_humanNoOnly services an agent can start using with no human setting up a key: probe-backed — its own (non-documentation) MCP server lists its tools to an unauthenticated client and the service needs no key (no auth, or a wallet), or one of its interfaces answers HTTP 402 to be paid per request
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. Changed1 schema field changed
    • addedInput schema / properties / no_human
      Added value: +{
+  "description": "Only services an agent can start using with no human setting up a key: probe-backed — its own (non-documentation) MCP server lists its tools to an unauthenticated client and the service needs no key (no auth, or a wallet), or one of its interfaces answers HTTP 402 to be paid per request",
+  "type": "boolean"
+}
  2. 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"
+]
  3. First observed

TDQS

A3.9/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 it discloses a genuinely non-obvious behavior: up to 3 paid promoted listings are pinned to the top and flagged with promoted:true/ad:true, with special rules for unfiltered vs category searches. It omits rate limits, auth requirements, and pagination/result-size behavior.

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?

Four sentences, front-loaded with the core purpose and filtering capability. Every sentence contributes (scope, filters, ad disclosure, ad exclusion), though the protocol acronym list in the description partially duplicates the schema.

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 12-parameter, no-output-schema, no-annotation search tool, the description covers scope, filter dimensions, and the important ad-injection behavior plus its result markers. It could say more about result shape/pagination, but the critical selection cues are present.

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 12 parameters (including protocol meanings and query semantics). The description adds only marginal guidance on the promoted filter, so the baseline 3 applies when the schema does the heavy lifting.

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?

States a specific verb (Search) and resource (the BotFriendly directory of bot-friendly services, APIs, and tools) with clear scope. It is readily distinguishable from sibling tools like get_service (single lookup) and submit_service (write).

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?

It enumerates available filter dimensions and gives one actionable instruction ('Use promoted=false to exclude ads'), which implies how to use the tool. However, it never states when to reach for this tool versus siblings such as get_service or get_featured, and gives no exclusions or prerequisites.

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
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources