Skip to main content
Glama

harvestpulse

Find local farms, farmers markets, and seasonal produce. Access organic certifications, food label decoders, and farm-to-table guides for informed food choices.

Instructions

HarvestPulse: Global farm-to-table and agricultural intelligence API. USDA + ERS data synthesis. Local food finder (farmers markets, CSAs, on-farm markets), seasonal produce calendars, organic certification lookup,

Coverage: Global

Endpoints: • find ($0.05): Local Farm & Market Finder • season ($0.05): Seasonal Produce Calendar • labels ($0.08): Food Label Decoder • organic ($0.08): Certified Organic Farm Finder • dirty-dozen ($0.05): Dirty Dozen & Clean Fifteen • food-hub ($0.08): Regional Food Hub Finder • regenerative ($0.10): Regenerative Agriculture Guide • designations ($0.10): Global Food Designations • agritourism ($0.05): Agritourism & U-Pick Finder • csa ($0.10): CSA Evaluation Guide • cost ($0.10): Local vs. Conventional Cost Analysis • roadmap ($0.15): Farm-to-Table Lifestyle Roadmap • food-preservation ($0.10): Food preservation guide • foraging-intel ($0.10): Foraging intelligence • livestock-basics ($0.10): Backyard livestock guide

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
zipNoUS ZIP code
cityNoCity name (optional filter)
langNoResponse language (default en)
typeNoType (plants, mushrooms, berries, all)
goalsNoSpecific goals (e.g. reduce pesticides, support local farms, eat seasonally)
itemsNoProduce items to compare (space or comma separated)
labelNoLabel to decode (e.g. free-range, natural, pasture-raised, grass-fed, non-GMO)
monthNoMonth (1-12). Defaults to current month.
queryNoSearch terms (e.g. beef, dairy, grain)
stateNo2-letter US state code (e.g. CA, TX, NY)
actionYesWhich endpoint to call. Options: find | season | labels | organic | dirty-dozen | food-hub | regenerative | designations | agritourism | csa | cost | roadmap | food-preservation | foraging-intel | livestock-basics
animalNoAnimal (chickens, goats, bees, etc.)
methodNoMethod (canning, fermenting, dehydrating, freezing, pickling)
radiusNoSearch radius in miles
seasonNoSeason (spring, summer, fall, winter)
climateNoClimate (temperate, arid, etc.)
countryNoCountry (for international calendar)
produceNoProduce to preserve
productNoProduct name (e.g. parmigiano-reggiano, champagne, prosciutto-di-parma, roquefort)
locationNoCity/state or region
quantityNoQuantity (e.g. small batch)
weekly_budgetNoWeekly food budget in USD
household_sizeNoNumber of people in household
land_size_sqftNoAvailable land in sq ft
Behavior2/5

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

No annotations provided, and the description does not disclose behavioral traits like authentication, rate limits, or side effects. It only lists endpoint costs, which is insufficient for a tool with 24 parameters.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is long due to listing all 15 endpoints with prices. While front-loaded with the domain, it could be more concise by grouping or omitting redundant details.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks guidance on how to compose parameters for each endpoint, what each endpoint returns, or relationships between parameters. For a complex tool with 24 params, it is incomplete.

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 all parameters. The description adds minimal extra meaning, mainly listing endpoint names with brief summaries, but does not elaborate on parameter usage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's domain as 'farm-to-table and agricultural intelligence' and lists specific endpoints, but lacks explicit differentiation from sibling tools, which are also in different domains.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance on when to use this tool versus alternatives, or when not to use it. It simply describes the API without context for selection.

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/GTCC777/mcp-pulsenetwork'

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