Skip to main content
Glama

Find the Juiciest Buns

minion_bun_hunt
Read-only

Discovers online food buns, filters irrelevant meanings, and scores each for relevance, juiciness, and orderability to crown a citation-backed winner.

Instructions

Run the gold Minion MCP demo in one tool call: discover food buns sold online, reject irrelevant meanings of 'buns', inspect product evidence, score relevance, juiciness, orderability, and proof, then crown a citation-backed winner.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
countryNoTwo-letter country code used to localize discovery.US
requestNoA food-bun shopping request. The gold demo works with the default.Find the Juiciest Buns on the internet
providerNoDiscovery backend. Auto uses Brave or SearXNG when configured; otherwise it uses the labeled starter catalog.auto
destinationNoOptional destination to include in discovery, such as California. Shipping is only scored when page evidence supports it.
safe_searchNoSearch-engine content filtering.strict
max_candidatesNoMaximum number of evidence-ranked bun candidates.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYes
requestYes
providerYes
rejectedYes
candidatesYes
searched_atYes
plain_englishYes
scoring_modelYes
minion_verdictYes
discovery_warningNo
catalog_updated_atNo
inspected_productsYes
inspection_warningNo
Behavior5/5

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

Annotations already mark it as read-only and open-world. The description adds significant behavioral context: it disambiguates 'buns' to food meanings, inspects product evidence, scores relevance and juiciness, and selects a citation-backed winner. This goes beyond annotations to explain the tool's internal logic.

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?

The description is a single, front-loaded sentence that efficiently conveys the entire tool workflow. Every clause adds value, with no wasted words.

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?

Given tool complexity (multi-step search, scoring, ranking) and presence of an output schema, the description covers the high-level flow adequately. It mentions key steps like discovery, rejection of irrelevant meanings, scoring, and crowning a winner, providing enough context for an agent.

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 has 100% coverage with descriptions for all 6 parameters. The description does not add parameter-specific semantics beyond what is in the schema, such as the default request or the provider backend. Baseline score of 3 is appropriate as the schema already explains parameters well.

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 clearly states the tool's specific purpose: discovering food buns, rejecting irrelevant meanings, inspecting evidence, scoring multiple attributes (juiciness, orderability, proof), and crowning a winner. It uses a specific verb (discover, crown) and differentiates from sibling tools like minion_web_search (general search) and minion_chat (chat).

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?

The description indicates it is for a specific demo ('Run the gold Minion MCP demo') and implies usage for finding the juiciest buns. However, it does not explicitly state when to use this tool vs alternatives or when not to use it, missing clear exclusion criteria.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/masonclewis/minion-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server