FieldMCP
PricingDocsChangelog
Sign inGet Started
FieldMCP

Connect your AI to farm data in minutes

Product

  • Pricing
  • Documentation
  • Changelog
  • Integrations

Company

  • About
  • Customers
  • Security
  • Contact
  • Support

Legal

  • Terms of Service
  • Privacy Policy
  • DPA
  • SLA

© 2026 FieldMCP. All rights reserved.

Status

Search Documentation

Search for a documentation page...

Getting Started

IntroductionQuickstart

Authentication

API KeysOAuth

Tools Reference

Overview
Diagnose FieldAnalyze YieldCompare FieldsGet Action PlanGet Rule DetailsSearch Rules
  1. Docs
  2. Farm Intelligence
  3. Diagnose Field

intel_diagnose_field

Run comprehensive field analysis and return all triggered diagnostic rules. Provide field data (yield history, soil tests, etc.) and receive a prioritized action plan with evidence-backed recommendations.

Parameters

Required

ParameterTypeDescription
fieldIdstringUnique field identifier
cropenumcorn, soybean, or wheat
targetCropYearnumberYear to analyze

Optional (improves analysis)

ParameterTypeDescription
fieldNamestringHuman-readable field name
acresnumberField size
locationobject{ state, region, latitude?, longitude?, countyFIPS? }
yieldHistoryarray[{ year, bushelsPerAcre, crop? }] — ideally 5+ years
countyYieldHistoryarray[{ year, averageYield }] — for benchmarking
soilTestobjectpH, organic matter, phosphorus, potassium, CEC, texture, drainage
compactionAssessmentobjectPenetrometer readings, ribbon test results
drainageAssessmentobjectSaturation duration, tile drainage status
rotationHistoryobject{ history: [{ year, crop, tillage }] }
plantingRecordobjectDate, variety, population, row spacing
diseaseAssessmentsarrayDisease observations with severity
pestCountsarrayPest observation data

The more data you provide, the higher the analysis confidence.

Usage

Minimal

{
  "fieldId": "field-001",
  "crop": "corn",
  "targetCropYear": 2025
}

With Yield and Soil Data

{
  "fieldId": "field-001",
  "fieldName": "North 40",
  "crop": "corn",
  "targetCropYear": 2025,
  "acres": 40,
  "yieldHistory": [
    { "year": 2024, "bushelsPerAcre": 165 },
    { "year": 2023, "bushelsPerAcre": 172 },
    { "year": 2022, "bushelsPerAcre": 168 }
  ],
  "soilTest": {
    "testDate": "2024-10-15",
    "fieldId": "field-001",
    "pH": 6.1,
    "texture": "silt_loam",
    "drainageClass": "moderately_well_drained"
  }
}

Response

{
  "error": false,
  "data": {
    "fieldId": "field-001",
    "fieldName": "North 40",
    "crop": "corn",
    "analysisDate": "2025-03-15T12:00:00Z",
    "overallConfidence": 0.72,
    "dataQuality": "PARTIAL",
    "diagnosticSummary": "3 issues identified. Primary concern: soil pH below optimal range.",
    "prioritizedActions": [
      {
        "priority": 1,
        "type": "ph",
        "severity": "moderate",
        "rationale": "Per DEC-001: Correct pH before fertilizer application",
        "prerequisites_met": true
      },
      {
        "priority": 2,
        "type": "nitrogen",
        "severity": "low",
        "rationale": "Yield history suggests potential nitrogen limitation",
        "prerequisites_met": true
      }
    ],
    "triggeredRules": [
      {
        "ruleId": "NUT-003",
        "name": "Suboptimal pH Detection",
        "confidence": 0.95,
        "message": "Soil pH 6.1 is below optimal range for corn (6.3-6.8)"
      }
    ],
    "missingData": [
      {
        "field": "compactionAssessment",
        "impact": "degraded",
        "message": "Cannot assess compaction without penetrometer data"
      }
    ]
  }
}

Data Quality

LevelMeaning
COMPLETEAll recommended data provided
PARTIALSome data missing — analysis runs but confidence is lower
INSUFFICIENTCritical data missing — results may be unreliable

Use intel_get_rule_details to understand why a specific rule fired.

ParameterTypeRequiredDescription
fieldIdstringRequiredUnique identifier for the field
fieldNamestringOptionalHuman-readable field name
acresnumberOptionalField size in acres
cropcorn | soybean | wheatRequiredTarget crop for analysis
targetCropYearnumberRequiredYear for which recommendations apply
locationobjectOptionalGeographic location details
yieldHistoryarrayOptionalHistorical yield records
countyYieldHistoryarrayOptionalCounty average yields for comparison
soilTestobjectOptionalMost recent soil test results
compactionAssessmentobjectOptionalCompaction evaluation
drainageAssessmentobjectOptionalDrainage status
rotationHistoryobjectOptionalCrop rotation history
varietyTrialDataobjectOptionalVariety trial data
plantingRecordobjectOptionalPlanting details
standAssessmentobjectOptionalStand count
soilConditionsAtPlantingobjectOptional
diseaseAssessmentsarrayOptional
tarSpotAssessmentobjectOptional
pestCountsarrayOptional
financialsobjectOptional
tenureobjectOptional

Try it

intel_diagnose_field

Sign in to try this tool

Sign in
Search OperationsAnalyze Yield