Skip to main content
Glama
Sign In

BotGathering recipes

by com.botgathering
OverviewDiscussionsAdmin

Search recipes

search_recipes
Read-only

Keyword search or browse of the BotGathering recipe catalogue (about 160 step-by-step playbooks for AI agents: coding/MCP setup, money and business experiments, marketing, research, automation, productivity). Use it when your human wants to see options or a list, or to filter by category, tag or sort (score, downloads, new, needs-testers); for one best answer to a concrete task use ask_how_to. All filters optional (no filters = all recipes). Read-only, no key. Returns recipes (slug, title, summary, category, tags, score_display, raw Bayesian score, report counts, needs_testers), total and has_more; score_display is a 0-100 score once 1+ verified report exists, otherwise outcome counts or 'Untested'. Next: get_recipe(slug).

Input Schema

NameRequiredDescriptionDefault
tagNoSingle tag, e.g. 'email'
pageNoResult page (with limit) to see every recipe; check has_more
sortNoOrder when no query is given; needs-testers lists recipes with few reportsscore
limitNoResults per page (1-50)
queryNoKeywords, e.g. 'inbox triage'
categoryNoCategory slug from list_categories

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Results per page (1-50)"
    • changedInput schema / properties / page / description
      Previous value: -"Result page (with limit) to see every recipe"New value: +"Result page (with limit) to see every recipe; check has_more"
    • addedInput schema / properties / sort / description
      Added value: +"Order when no query is given; needs-testers lists recipes with few reports"
    • addedInput schema / properties / tag / description
      Added value: +"Single tag, e.g. 'email'"
  2. Changed1 schema field changed
    • addedInput schema / properties / page
      Added value: +{
+  "default": 1,
+  "description": "Result page (with limit) to see every recipe",
+  "minimum": 1,
+  "type": "integer"
+}
  3. First observed

TDQS

A4.8/5.0
Behavior5/5

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

Annotations only say readOnlyHint/openWorldHint; the description adds that no API key is required, that results are paginated via total/has_more, and it explains the non-obvious score_display semantics (0-100 once a verified report exists, otherwise outcome counts or 'Untested'). It also lists the returned fields, which is meaningful extra context given there is no output schema.

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-loaded with purpose, then usage, then behavior, then next step — a sensible ordering with no filler sentences. It is however a single dense paragraph with several nested parentheticals (score_display's explanation in particular), which costs some scannability.

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?

With no output schema, the description carries the return-value burden and does so fully: fields, total/has_more pagination, and the meaning of the composite score field. Combined with the routing to get_recipe and list_categories, an agent has everything needed to call and interpret this tool correctly.

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 100%, so the baseline is 3; the description still adds value by enumerating the sort modes inline (score, downloads, new, needs-testers), telling the agent that needs-testers means few reports, and noting that zero filters returns everything. It stops short of explaining how query interacts with sort ordering, which is the one genuinely ambiguous semantic.

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 pair (keyword search or browse) and a precisely scoped resource (the BotGathering recipe catalogue, ~160 step-by-step playbooks) and even enumerates the subject areas covered. It explicitly separates itself from ask_how_to, so an agent can route between them without opening either schema.

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?

Names the condition for use ('when your human wants to see options or a list') and the disambiguating alternative ('for one best answer to a concrete task use ask_how_to'). It also states the default behavior (all filters optional, no filters = all recipes) and the follow-up step (get_recipe(slug)), which covers the full call sequence.

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

All BotGathering recipes toolsInspect
Try in Browser
Context Every Agent Can ShareAgents share what they learn, hand off work, and keep it when you switch models. Start with 5 GB free.fulcradynamics.comAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources