Plan, measure, and record field work for your AI agent.

Work out irrigation, seeding, fertilizer and growing degree days with stated formulas
Set the spray limits, buffers and approvals your agent must follow
Measure fields and do tank math from the label rates you enter

View raw file Download Add to an MCP client

AGRICULTURE.mdv1.0

name:: agriculture
description:: Field math and work rules for farm agents. Units first, chemical rates only from the product label, spray only inside a weather window, ask before chemical applications and large irrigation or nitrogen changes, and record every application. Use when a task plans, measures or records field work: spraying, irrigation, seeding, fertilizer, growing degree days or field area.
license:: MIT
metadata:
version:: "1.0"
homepage:: https://agriculture.md
api:: https://agriculture.md/api/v1 (optional, no key, stores nothing)
terms:: https://agriculture.md/terms

Agriculture

Provided as is, at your own risk: figures are estimates from the numbers you use and may be wrong or out of date, and nothing here is agronomic, legal, regulatory or safety advice. Follow the product label and local law, and check with a qualified agronomist. Terms: https://agriculture.md/terms.

Plan, measure and record field work with the person's own numbers. Never pick a product or a rate. Ask before anything goes on a field. Show your math once, in a short block, with units on every number. Skip routine narration.

When this file has a "Your rules" section, those rules win over the defaults below, unless the label or the law is stricter. Settings you drafted or changed yourself count only after the person says yes.

1. Units first

Write the unit on every number: ha or ac, mm or in, kg/ha or lb/ac, L/ha or gal/ac, km/h or mph, degrees C or F. A number without a unit is not usable.

Convert before you calculate, never after. Exact factors: 1 ac = 0.40468564224 ha; 1 in = 25.4 mm; 1 US gal = 3.785411784 L; 1 lb = 0.45359237 kg; 1 lb/ac = 1.12085 kg/ha; 1 gal/ac = 9.35396 L/ha; 1 mph = 1.609344 km/h.

Watch the common traps: US gallons vs other gallons, fluid ounces vs dry ounces, P vs P2O5 and K vs K2O (P = P2O5 x 0.4364, K = K2O x 0.8301), product rate vs active ingredient rate, and per-hectare vs per-acre.

When two sources disagree on a unit, stop and ask.

2. The label sets the rate

For any pesticide, adjuvant or other regulated product, the product label is the legal limit. Take every rate, interval, restriction and buffer from the label the person has, and quote where it came from.

Never exceed a label rate, never suggest a rate, and never fill a missing rate with a guess, a typical value or one from memory. If the rate is missing, ask.

Never pick a product or a tank mix for the person. Never change a rate the person gave you; if it looks wrong (a unit slip, or above the label maximum), stop and ask.

Optional tool for tank math only: POST https://agriculture.md/api/v1/spray_mix with

{ "area": 32, "carrier_rate": 100, "tank_size": 2000, "products": [{ "rate": 1.5, "unit": "l_per_ha", "label_max": 2 }] }

. Send label_max from the label so the tool can flag a rate above it.

3. Spray only inside a weather window

Before any spray job, check wind (gusts included), rain in the hours after the job, temperature and any inversion risk against the person's limits and the label. Use the person's own reading or forecast, and say which and when.

If any limit is not met, or you can't tell, don't plan the job for that time. Say which limit failed and when it next looks met.

Keep the buffers from water, wells, drains, homes and sensitive crops that the label, local law and the person's rules set. The widest one applies.

4. Water

Water need = reference evapotranspiration x crop coefficient x days, less effective rain, divided by application efficiency. The person gives each figure.

Optional tool: GET https://agriculture.md/api/v1/irrigation?et0=6&kc=1.1&days=3&effective_rain=5&efficiency_pct=85&area=20&flow=120. It returns depth, volume and run time.

Ask before any event deeper than the person's limit, before any schedule change past it, and whenever water rights or local limits apply.

5. Nutrients

Product rate = nutrient target / (nutrient % / 100). The target comes from the person, a soil test or their agronomist; never from you.

Count the other nutrients the product delivers, and keep each nitrogen application under the person's limit and any local limit.

Optional tool: GET https://agriculture.md/api/v1/fertilizer_rate?nutrient=p2o5&target=50&grade=18-46-0&area=20.

6. Seeding, growing degree days and area

Seeds per area = target stand / (germination x emergence). Seed weight = seeds / (seeds per kg x purity). Take germination, purity and seed count from the seed tag. Tool: seeding_rate.

Growing degree days: state the method, the base and the cap every time, and use the base and cap the person or their agronomist gives for the crop. Tool: gdd.

Field area: measure from the person's boundary points, in order around the edge, and say the result is an estimate. Tool: field_area. Use the area the person confirms for any rate or total.

7. Ask before you act

Every chemical application needs a yes from the person first: product, label rate, field, area, timing and weather. A calculation is never a yes.

Also ask before any irrigation or nitrogen amount over the person's limits, any work near water inside a buffer, and anything the label or local law requires a licensed person to do.

Never control equipment, place orders or apply anything yourself unless the person set that up and said yes for this job.

8. Record every application

Write a record as soon as the job ends: date and times, field, area treated, product and label registration number, rate, total amount, carrier volume, who applied it, who approved it, and the weather at the time.

Keep records in the person's own system and format. Local law may set what must be recorded and for how long; ask the person.

9. Local rules and an agronomist

Laws on chemicals, nutrients, water and buffers differ by place and change. Follow the law where the field is. When you are not sure what applies, say so and ask.

Suggest the person check plans with a qualified agronomist or local adviser, especially new products, new fields, high rates or sensitive areas.

10. Report

Five lines at most: what was calculated, the result with units, the inputs and where each came from, what you could not check, and what needs a yes.

Works offline in any agent. Same file at /agriculture.md.

Customize

Your field rules, in one file.

8 settings in 4 groups. Start from a preset, change anything, and your settings are written into AGRICULTURE.md. Every setting is a number or a fixed choice, so a shared link can’t slip words into the file. The same settings work as URL parameters, MCP prompt arguments, the build_settings tool and /api/v1/build_settings.

Start from

Approvals, records and units. No numeric limits: the label and local law set them.

Spraying

Weather limits and water buffers for any spray job.

0 of 3 set

Max wind speed for sprayingkm/hRain-free hours needed after sprayinghBuffer distance from waterm

3 of 8 set

AGRICULTURE.md · your settings

Your rules

Set by the person you work for, and only that person can change them. Rules an agent drafted count only after that person says yes. Where a rule here and the rest of this file differ, the stricter one wins. The product label and the law where the field is always win over both. If a rule blocks the task, stop and ask; don't work around it.

Approvals and records

Get a yes from the person before every chemical application: product, label rate, field, area, timing and weather. No exceptions, even for a repeat job.

Record every application: date and start and end time, field, area treated, product and its label registration number, rate, total amount, carrier volume, who applied it and who approved it, plus wind speed and direction, temperature, humidity and the equipment used.

How to write numbers

The measurement system the person you work for uses. Follow this unless a rule above says otherwise.

Measurement system

Write numbers in metric (hectares, millimetres, kilograms, litres, km/h, degrees Celsius). Give imperial in brackets when a label or record uses it.

The full skill, with your settings at the top.

mkdir -p ~/.claude/skills/agriculture && curl -fsSL "https://agriculture.md/agriculture.md?chem_approval=every_application&records=with_conditions&units=metric" -o ~/.claude/skills/agriculture/SKILL.md

Linkhttps://agriculture.md/agriculture.md?chem_approval=every_application&records=with_conditions&units=metric

Copy as JSON

The same settings as one JSON object. It feeds the build_settings tool or POST /api/v1/build_settings.

3 of 8 settings set. Anything not set follows the skill’s own rules.

Tools

Field math your agent can call.

Every tool works with the numbers you send, checks units, and states its formula. Results come back in metric and imperial, with what the tool can't check. No tool suggests a chemical or fertilizer rate.

Spray tank mix from label rates

Tank math for a spray job: total spray volume, number of tank loads, area per tank, and how much of each product goes in each full tank and the last partial tank, from your area, carrier volume, tank size and the product rates you take from each label. Flags any rate above the label maximum you enter. It never suggests a rate, a product or a mixing order, and it checks no label, weather or compatibility.

unitsUnit system for the numbers you send: metric or imperial. Default metric. Results come back in both.arearequiredArea to spray: ha (metric) or ac (imperial).carrier_raterequiredTotal spray volume per area from the label or your calibration: L/ha (metric) or US gal/ac (imperial).tank_sizerequiredUsable tank volume: L (metric) or US gal (imperial).productsrequiredProducts in the tank: [{ label?, rate, unit, label_max? }]. rate is the label rate you chose, per area. unit is one of l_per_ha, ml_per_ha, kg_per_ha, g_per_ha, gal_per_ac, qt_per_ac, pt_per_ac, fl_oz_per_ac, lb_per_ac, oz_per_ac. label_max is the label's maximum rate in the same unit, if you want it checked.

Run the tool to see a result. Estimates only; check them yourself.

POST /api/v1/spray_mix

{
  "units": "metric",
  "area": 32,
  "carrier_rate": 100,
  "tank_size": 2000,
  "products": [
    {
      "label": "Product A",
      "rate": 1.5,
      "unit": "l_per_ha",
      "label_max": 2
    },
    {
      "label": "Product B",
      "rate": 40,
      "unit": "g_per_ha"
    }
  ]
}

curl -s https://agriculture.md/api/v1/spray_mix -H 'content-type: application/json' -d '{"units":"metric","area":32,"carrier_rate":100,"tank_size":2000,"products":[{"label":"Product A","rate":1.5,"unit":"l_per_ha","label_max":2},{"label":"Product B","rate":40,"unit":"g_per_ha"}]}'

An agent can talk about farming. Field math has to be exact.

Ask a language model for a tank mix or an irrigation run time and you get a plausible number. One slipped unit (gallons for litres, acres for hectares, P for P2O5) moves the answer by 2 to 10 times, and on a field that means wasted product, runoff or crop damage. This file gives an agent fixed formulas with units on every number, your limits written into its instructions, and two hard rules: rates come only from the label, and nothing goes on a field without a yes.

Units first: every tool takes metric or imperial and returns both, with exact conversion factors.
The label sets the rate: spray_mix never suggests a rate and flags any rate above the label maximum you enter.
Your limits, in writing: wind, rain-free hours, buffers, irrigation depth and nitrogen thresholds go into the skill.
Same answer everywhere: the page, the API and the MCP tools run the same code, and nothing is stored.

Use it in your stack

Paste it, install it, or call it.

The skill alone gives an agent the method. The MCP server and API add the tools and your settings. No key, no account.

Paste the prompt into a system prompt or project instructions. Or keep the file in the repo and point AGENTS.md at it.

terminal

curl -fsSL https://agriculture.md/agriculture.md -o AGRICULTURE.mdecho "Whenever a task plans, measures or records field work: spraying, irrigation, seeding, fertilizer, growing degree days or field area, follow AGRICULTURE.md." >> AGENTS.md

For agents that read a skills folder: install the skill so it loads when the topic comes up, and add the MCP server for the tools.

terminal

# The skillmkdir -p ~/.claude/skills/agriculturecurl -fsSL https://agriculture.md/agriculture.md -o ~/.claude/skills/agriculture/SKILL.md# Tools: spray_mix, irrigation, gdd, fertilizer_rate, seeding_rate, field_area, build_settingsclaude mcp add --transport http agriculture https://agriculture.md/mcp

For editors that read an mcp.json file: add the remote MCP server to the project, then paste the prompt into your rules.

mcp.json

// .cursor/mcp.json{ "mcpServers": { "agriculture": { "url": "https://agriculture.md/mcp" } } }// .vscode/mcp.json{ "servers": { "agriculture": { "type": "http", "url": "https://agriculture.md/mcp" } } }

Any client that speaks remote MCP over HTTP can add it as a custom connector. Read-only, so there is nothing to authorize.

connector

url: https://agriculture.md/mcptransport: streamable-http   # stateless, JSON responsestools: spray_mix, irrigation, gdd, fertilizer_rate, seeding_rate, field_area, build_settingsprompts: agriculture   # the skill, with your settings

GET with query parameters or POST a JSON body. CORS open. An OpenAPI document is at /openapi.json.

terminal

# Every tool: GET or POST https://agriculture.md/api/v1/<tool>curl -s https://agriculture.md/api/v1 | jq '.tools[].name'curl -s "https://agriculture.md/api/v1/irrigation?units=metric&et0=6&kc=1.1&days=3&effective_rain=5&efficiency_pct=85&area=20&flow=120&max_depth=15" | jq .summarycurl -s "https://agriculture.md/api/v1/settings" | jq '.presets[].id'

Quickest start:claude mcp add --transport http agriculture https://agriculture.md/mcp

Example code

Call it from your own code.

Working calls against the API. The full reference is at /api/v1 and /openapi.json.

Call a tool by GET, then by POST. No key; nothing is stored.

call.sh

# Call a tool by GET, then by POST. No key; nothing is stored.curl -s "https://agriculture.md/api/v1/irrigation?et0=6&kc=1.1&days=3&effective_rain=5&efficiency_pct=85&area=20&flow=120&max_depth=15" | jq .summarycurl -s https://agriculture.md/api/v1/spray_mix \  -H 'content-type: application/json' \  -d '{"area":32,"carrier_rate":100,"tank_size":2000,"products":[{"label":"Product A","rate":1.5,"unit":"l_per_ha","label_max":2}]}' \  | jq '{summary, tank_loads, products}'# The skill with your own choices written incurl -s "https://agriculture.md/agriculture.md?preset=recommended&units=imperial&chem_approval=every_load" -D - -o SKILL.md | grep -i x-settings

Plan a spray job: field area from boundary points, then tank math over MCP.

plan.mts

// Plan a spray job: field area from boundary points, then tank math over MCP.const call = async (name: string, args: object) => {  const res = await fetch("https://agriculture.md/mcp", {    method: "POST",    headers: { "content-type": "application/json", accept: "application/json" },    body: JSON.stringify({ jsonrpc: "2.0", id: 1, method: "tools/call", params: { name, arguments: args } }),  });  const { result } = await res.json();  return result.structuredContent;};const field = await call("field_area", {  points: [    { lat: 40.0, lon: -95.0 },    { lat: 40.0, lon: -94.9953 },    { lat: 40.0036, lon: -94.9953 },    { lat: 40.0036, lon: -95.0 },  ],});console.log(field.summary);// Rates come from the product label, never from the tool.const mix = await call("spray_mix", {  area: field.area.ha,  carrier_rate: 100,  tank_size: 2000,  products: [{ label: "Product A", rate: 1.5, unit: "l_per_ha", label_max: 2 }],});console.log(mix.summary); // then ask the person for a yes before mixing

FAQ

Does it recommend products or rates?

No. agriculture.md never recommends a product or rate, applies anything or controls equipment. Rates come from the product label and from you. The tools only do the arithmetic and flag a rate above a label maximum you enter.

If a result shows no flag, is the job safe or legal?

No. A result is arithmetic on your numbers. It does not check the label, the weather, the law where the field is, compatibility or calibration. Read the label, follow local law, and check with a qualified agronomist or licensed applicator.

Where do the weather and crop numbers come from?

From you. The site has no weather feed, no product database and no crop tables. Reference evapotranspiration, crop coefficients, base temperatures, seed tags and label rates are numbers you enter.

Why do the presets leave the numeric limits empty?

Because wind, rain-free hours, buffers, irrigation depth and nitrogen limits depend on the label, local rules and the field. This site suggests none. Enter the limits from your labels, your local rules and your agronomist.

How accurate is field_area?

It uses an equal-area projection on the standard GPS reference ellipsoid, which is very close for field-sized boundaries. The real limit is your points: their accuracy, their order, and anything inside the boundary that is not cropped.

Is this advice?

No. Nothing here is agronomic, legal, regulatory or safety advice. Follow the product label and the law where you work, and check with a qualified agronomist. AGRICULTURE.md is a method for software agents plus calculators that work on the numbers you send. Results are estimates that may be wrong. Check them yourself, and ask a qualified person when it matters.

Does it name brands or show prices?

No. Settings and tools use generic terms, and agriculture.md shows no prices, rates or other outside data. Every number a tool uses comes from your request or from a formula the tool states.

Can an agent set up its own settings?

It can draft them: the same settings work as URL parameters, MCP prompt arguments and the build_settings tool. The skill and the tool both say that drafted settings count only after the person says yes. Nothing technical stops an agent from ignoring that, so read what it sends you.

Does a tool result mean something is approved?

No. Tools calculate, compare and check. They don’t approve, enforce or certify anything, and they can be wrong.

Can I change everything?

Yes. Start from a preset, change any setting above, and your choices are written into the file. Or edit the Markdown yourself. It’s MIT; keep your copy next to your code.

Do you track anything?

We count page views, copies, skill fetches and API and MCP calls to learn what is useful, without cookies or stored IP addresses. We never record your settings values or what you send to a tool. Details in the terms.