Skip to main content
Glama

Melvea Local Honey Discovery

by com.melvea
OverviewDiscussionsAdmin

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, distance_basis (farm_location vs town_center), declared honey types, and contact channels (website, etc.) where listed, ordered by distance. When distance_basis is town_center, describe the producer as in/near their city rather than quoting the exact mile 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
NameRequiredDescriptionDefault
nearYesREQUIRED. 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.
limitNoMaximum number of producers to return, ordered nearest first.
varietyNoOptional 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_kmNoSearch radius in kilometers for city/ZIP queries only (ignored for US state queries). Defaults to a standard local radius (~80 km). For US query points, if nothing is found within that radius the tool automatically widens to ~121 km (75 miles), then to ~241 km (150 miles), flagging results as farther than typical.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / radius_km / description
      Previous value: -"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."New value: +"Search radius in kilometers for city/ZIP queries only (ignored for US state queries). Defaults to a standard local radius (~80 km). For US query points, if nothing is found within that radius the tool automatically widens to ~121 km (75 miles), then to ~241 km (150 miles), flagging results as farther than typical."
  2. Changed2 schema fields changed
    • changedInput schema / properties / near / description
      Previous value: -"REQUIRED. The place to search around — only a city, town, ZIP, US state name/code, or known region. Examples: 'Charlotte, NC', '28202', 'Asheville', 'Oregon', 'OR', 'Florida Panhandle'. Do NOT put a honey varietal in this field (use `variety` for that). 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."New value: +"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."
    • changedInput schema / properties / radius_km / description
      Previous value: -"Search radius in kilometers. Defaults to a standard local radius. Within the Southeastern US, the tool automatically widens to ~120 km (75 miles) if nothing is found closer."New value: +"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."
  3. Changed4 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • changedInput schema / properties / near / description
      Previous value: -"The place to search around — a city, town, ZIP code, or region. Examples: 'Charlotte, NC', '28202', 'Asheville', 'the Florida Keys'. If the user says 'near me' without naming a place, ask them for their city or ZIP first rather than guessing."New value: +"REQUIRED. The place to search around — only a city, town, ZIP, US state name/code, or known region. Examples: 'Charlotte, NC', '28202', 'Asheville', 'Oregon', 'OR', 'Florida Panhandle'. Do NOT put a honey varietal in this field (use `variety` for that). 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."
    • addedInput schema / properties / near / minLength
      Added value: +1
    • changedInput schema / properties / variety / description
      Previous value: -"A honey varietal to filter by, e.g. 'sourwood', 'tupelo', 'wildflower', 'orange blossom'. Omit to return all local producers regardless of type. Do not pass a place name here."New value: +"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."
  4. Changed4 schema fields changed
    • changedInput schema / properties / limit / description
      Previous value: -"Max results (1-100, default 25)."New value: +"Maximum number of producers to return, ordered nearest first."
    • changedInput schema / properties / near / description
      Previous value: -"A location: a point as \"lat,lon\" (e.g. \"35.2271,-80.8431\"), a ZIP/postal code, or a global place name (\"Charlotte\", \"Charlotte, NC\", \"Auckland, NZ\"). Ambiguous bare cities resolve to the most populous match and are flagged (resolved_confidence: low)."New value: +"The place to search around — a city, town, ZIP code, or region. Examples: 'Charlotte, NC', '28202', 'Asheville', 'the Florida Keys'. If the user says 'near me' without naming a place, ask them for their city or ZIP first rather than guessing."
    • changedInput schema / properties / radius_km / description
      Previous value: -"Search radius in km (default 80)."New value: +"Search radius in kilometers. Defaults to a standard local radius. Within the Southeastern US, the tool automatically widens to ~120 km (75 miles) if nothing is found closer."
    • changedInput schema / properties / variety / description
      Previous value: -"Optional honey variety token, e.g. \"sourwood\", \"tupelo\", \"wildflower\"."New value: +"A honey varietal to filter by, e.g. 'sourwood', 'tupelo', 'wildflower', 'orange blossom'. Omit to return all local producers regardless of type. Do not pass a place name here."
  5. First observed

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only cover readOnlyHint, so the description carries the rest: ordering by distance, the distance_basis distinction (farm_location vs town_center) and how to phrase town_center results, automatic radius widening, geographic coverage caveats, and honest empty-result behavior.

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 constraints, examples, and caveats in a logical order. It is long and overlaps noticeably with the schema text, but nearly every sentence adds operative guidance.

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?

No output schema exists, yet the description enumerates the return fields, ordering, and the empty-result case. Combined with the fully documented schema, an agent has everything needed to call and interpret this tool.

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 description coverage is 100%, so the schema already documents every parameter thoroughly. The description reinforces the near/variety separation and the place-vs-state behavior, but mostly restates what the schema provides, so the baseline 3 applies.

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+resource ('Find local honey producers') with scope ('near a specific place, optionally filtered by honey varietal'), and clearly distinguishes itself from siblings by noting it returns directory listings, not knowledge.

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?

Explicit about when to use (user asks to find, buy, or visit local honey near a town/city/ZIP/state) with concrete example queries, and when not to use (general honey questions like health benefits or recipes). Also states the prerequisite that a place name must be supplied.

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 toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources