Melvea Local Honey Discovery

find_local_producers

Read-only

Find local honey producers near a specific place, optionally filtered by honey varietal. Requires a place name in near — never call this tool without one. Returns producer name, location, distance, declared honey types, and contact channels (website, etc.) where listed, ordered by distance. Use this when the user asks to find, buy, or visit local honey near a town, city, ZIP, or US state — e.g. 'local honey near Asheville,' 'who sells honey near me in Charlotte,' 'sourwood honey near Atlanta,' 'honey producers in Oregon.' Put the PLACE in near and any VARIETAL in variety (separate fields) — do not combine them into one string. US state names (e.g. 'Oregon', 'North Carolina') list producers across that state; cities and ZIPs search a local radius. Named sub-state regions (e.g. 'Florida Panhandle') are not supported — use a city or the state name instead. Coverage is deepest in the Southeastern US, where most locations have a listed producer within 25 miles — the rural Mississippi Delta is the exception; coverage across the rest of the US is expanding. Don't use this for general honey questions (what is sourwood honey, health benefits, recipes) — it only returns directory listings, not knowledge. If no producer is listed nearby, the tool returns an honest empty result with a coverage note; relay that rather than inventing producers.

Input Schema

TableJSON Schema

Name	Required	Description
`near`	Yes	REQUIRED. The place to search around — a city, town, ZIP, or US state name/code. Examples: 'Charlotte, NC', '28202', 'Asheville', 'Oregon', 'OR', 'North Carolina'. Do NOT put a honey varietal in this field (use `variety` for that). Do NOT pass named sub-state regions (e.g. 'Florida Panhandle') — ask for a city or the state instead. If the user has not named a place (e.g. only said 'near me'), ask them for their city, ZIP, or state BEFORE calling this tool — do not invent a location and do not call with an empty near.
`limit`	No	Maximum number of producers to return, ordered nearest first.
`variety`	No	Optional honey varietal filter, e.g. 'sourwood', 'tupelo', 'clover', 'wildflower', 'orange blossom'. Pass this SEPARATELY from `near` — e.g. near='Asheville, NC' and variety='sourwood', never near='Asheville, NC sourwood'. Omit to return all local producers regardless of type. Do not pass a place name here.
`radius_km`	No	Search radius in kilometers for city/ZIP queries only (ignored for US state queries). Defaults to a standard local radius. Within the Southeastern US, the tool automatically widens to ~120 km (75 miles) if nothing is found closer.

TDQS

A4.8/5.0

Behavior5/5

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

Discloses read-only nature (consistent with readOnlyHint), coverage limitations, auto-widening radius, exceptions (Mississippi Delta), and behavior on empty results. No contradiction with annotations.

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?

Well-structured with key points first, then examples, then limitations. A bit lengthy but every sentence adds necessary detail. No redundancy.

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?

Covers return fields (name, location, distance, etc.), ordering, and behavior on empty results despite no output schema. Complete for a directory lookup tool.

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 descriptions are complete (100% coverage), but the description adds extra context: not to combine near and variety, radius_km defaults, and ignored for state queries. Adds value beyond 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?

The description clearly states it finds local honey producers near a place, optionally filtered by varietal. It distinguishes from siblings (fetch, get_producer, search) by being specific to local directory listings, and explicitly says not to use for general honey questions.

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?

Provides explicit when-to-use (local honey queries) and when-not-to-use (general honey knowledge). Gives concrete examples and explains what to do if no place is provided, e.g., ask user for city/ZIP.

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

All Melvea Local Honey Discovery tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.4/5.0

Disambiguation5/5

Each tool has a clearly distinct purpose: search for free-text, find_local_producers for location-based discovery, get_producer for detail by slug, fetch for full record by id. No overlap or ambiguity.

Naming Consistency3/5

Naming is mixed: single-word verbs (fetch, search) alongside verb_noun patterns (find_local_producers, get_producer). While understandable, it lacks a consistent convention.

Tool Count5/5

Four tools is well-scoped for a honey producer directory, covering search, location-based discovery, and detailed retrieval without bloat.

Completeness4/5

The tool set covers core discovery and detail retrieval. Minor gaps like listing honey varietals or browsing without location exist, but the primary workflows are complete.

Resources

Need Help?