Skip to main content
Glama

BotFriendly

by xyz.botfriendly
OverviewDiscussionsAdmin

submit_service

Submit a service to the BotFriendly directory. There is no review queue: each interface URL must be on the service's own domain, or linked from the service's own site, and is fetched during the call; the listing publishes immediately if its MCP server, OpenAPI spec or API completes a handshake — one of has_mcp_server, has_openapi_spec or has_api is required; llms.txt, skill files and feeds only add badges. The url must be the product, not an article (/blog/, /news/ and similar are rejected), and a domain can add at most 2 listings a day and 3 in total. Every listing needs an icon — pass icon_url, or leave it out and the service's own site is checked for one.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesService URL
nameYesService name
tagsNo
api_urlNoRequired when has_api is true: the API's base URL (api.example.com, or a path under /api or /v1). It must answer in JSON. On the service's own domain, or linked from its site.
has_apiNo
categoryYesCategory id (see list_categories)
icon_urlNoLink to the service's icon (PNG, JPEG, SVG or WebP, under 1MB). Fetched and re-hosted, downscaled to 512px. Omit it and the service's site is checked for one.
accepts_mppNo
auth_methodNoAuth method
descriptionYesShort description (max 120 chars)
icon_base64NoAlternative to icon_url: the image inline, as a data: URI or bare base64.
accepts_x402No
billing_modelNo
contact_emailNoContact email for verification
has_mcp_serverNo
mcp_server_urlNoRequired when has_mcp_server is true. On the service's own domain, or linked from its site.
has_openapi_specNo
openapi_spec_urlNoRequired when has_openapi_spec is true. On the service's own domain, or linked from its site.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / api_url
      Added value: +{
+  "description": "Required when has_api is true: the API's base URL (api.example.com, or a path under /api or /v1). It must answer in JSON. On the service's own domain, or linked from its site.",
+  "type": "string"
+}
    • addedInput schema / properties / has_api
      Added value: +{
+  "type": "boolean"
+}
    • changedInput schema / properties / mcp_server_url / description
      Previous value: -"Required when has_mcp_server is true, and must be on the service's own domain."New value: +"Required when has_mcp_server is true. On the service's own domain, or linked from its site."
    • changedInput schema / properties / openapi_spec_url / description
      Previous value: -"Required when has_openapi_spec is true, and must be on the service's own domain."New value: +"Required when has_openapi_spec is true. On the service's own domain, or linked from its site."
  2. Changed2 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Category slug"New value: +"Category id (see list_categories)"
    • addedInput schema / properties / category / enum
      Added 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

A4.5/5.0
Behavior5/5

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

With no annotations, the description carries the full burden and delivers: no review queue, immediate publication on handshake completion, URLs fetched during the call, own-domain/linked-from-site constraints, and explicit rate limits (2/day, 3 total per domain). It also discloses rejection rules for article-like paths and the icon fallback behavior — unusually complete for an unannotated mutation tool.

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?

Front-loads the purpose, then packs validation rules, requirements and limits into one dense paragraph with essentially no filler. It would read better as short bullets given the number of distinct constraints, but every sentence carries information.

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 18-parameter submission tool with no annotations and no output schema, the description covers the rules an agent needs to construct a valid call: required capability flag, URL legitimacy, domain limits and icon handling. It stops short of describing failure modes or the response after a rejected/held submission, but the essential pre-call knowledge is present.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 61%, above the baseline threshold, and the description adds real meaning on the parameters that matter: the url must be the product not an article, the three capability booleans gate listing success, api_url must answer JSON, and icon_url vs omission triggers a site lookup. Secondary fields (tags, accepts_mpp, accepts_x402, billing_model, auth_method, contact_email) are left to the schema.

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?

Opens with a specific verb+resource ('Submit a service to the BotFriendly directory') and immediately scopes it to a directory-listing write action, which is clearly distinct from read-oriented siblings like get_service, search_services and list_categories. No sibling does submission, and the description makes the tool's identity unmistakable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Gives rich conditional guidance: at least one of has_mcp_server/has_openapi_spec/has_api is required, api_url/mcp_server_url/openapi_spec_url become mandatory with the corresponding boolean, and icon_url may be omitted. It does not name a competing sibling or an explicit 'use this instead of X' routing, but no sibling overlaps, so the omission is minor.

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