Skip to main content
Glama
mil0s2

botgathering-recipes

by mil0s2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Search recipes

search_recipes
Read-onlyIdempotent

Search the BotGathering recipe catalogue by keyword, category or tag, sorted by score, downloads, newest or needs-testers, to browse or page through recipe options.

Instructions

Search or browse the BotGathering recipe catalogue by keywords, category or tag, sorted by score, downloads, newest or needs-testers. Use it to list options or page through everything; for a single best answer to a task use ask_how_to. All filters are optional (no filters = all recipes); the category is checked against list_categories. Read-only, no key. Returns a readable list plus structured data: recipes (slug, title, summary, category, tags, score_display, reports, needs_testers, url), total, page and has_more. score_display is a 0-100 score once a verified report exists, otherwise outcome counts or 'Untested'; untested recipes need reports most, failures included.

Input Schema

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

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real context beyond them: 'no key' (auth requirement), the needs-testers semantics, and the meaning of score_display (0-100 only after a verified report). It does not discuss rate limits or result caps beyond what the schema states.

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 and the sibling alternative, then return shape. Slightly dense in the score_display clause, but every sentence carries information an agent needs given there is no output schema.

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 six params and no output schema, the description compensates by enumerating the returned fields (slug, title, summary, category, tags, score_display, reports, needs_testers, url) plus total/page/has_more for pagination. Nothing an agent needs to invoke or interpret results is missing.

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 meaning beyond the schema: that filters are optional and omitting all returns the full catalogue, and that category is a slug validated against list_categories, which reduces invalid calls.

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/browse) plus resource (BotGathering recipe catalogue) and enumerates the supported filter and sort dimensions. It explicitly distinguishes itself from ask_how_to for single-answer lookups, so an agent can choose without opening schemas.

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?

Gives the positive case (list options / page through everything) and names the alternative (ask_how_to) with the condition that selects it. It also states all filters are optional and that no filters returns everything, and that category values come from list_categories.

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

Deploy Server

Other Tools