Deere Ops Center MCP

Overview Schema Source Related Servers Discussions Admin

jd_list_field_operations

Read-only

Retrieve tillage, seeding, application, and harvest operations for a John Deere field to access dates, products, machines, and measurement totals.

Instructions

List the field operations recorded on one field: tillage, seeding, application, harvest.

    Returns `operations`, each with `fieldOperationType`, `cropSeason`, `cropName`,
    `startDate`, `endDate`, `products`, `varieties`, `fieldOperationMachines` and the
    measurement totals Deere recorded (area, total and average material, seeding rate,
    yield), plus `measurements_url` and `shapefile_available`. Get `org_id` from
    jd_list_organizations and `field_id` from jd_list_fields; each operation's `id` is the
    `operation_id` for jd_get_field_operation_measurements and the shapefile download.
    One crop season per call is the normal use (`crop_season`). `start_date` and `end_date`
    form a date filter that Deere limits to a 7-day window per request.

Input Schema

TableJSON Schema

Name	Required	Description
`org_id`	Yes	Organization ID from jd_list_organizations.
`end_date`	No	End of a date window, ISO 8601 (for example 2024-05-07T23:59:59Z).
`field_id`	Yes	Field ID from jd_list_fields.
`start_date`	No	Start of a date window, ISO 8601 (for example 2024-05-01T00:00:00Z).
`crop_season`	No	Crop season year to return, for example 2024. Omit for all.
`operation_type`	No	Only operations of this type. Omit for all types.

Output Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Oct 16, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations provide readOnlyHint/openWorldHint, and the description adds a real constraint beyond them: Deere limits the start_date/end_date filter to a 7-day window per request. It also discloses that shapefile availability is signaled via `shapefile_available`, which is useful behavioral context for downstream chaining.

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-loads the purpose, then usage, then constraints in a logical order. The long enumeration of return fields is somewhat verbose given an output schema already exists, but it is dense and non-repetitive rather than padded.

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

Completeness4/5

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

Because an output schema exists, explaining return values is not strictly necessary, yet the description covers the key shape and the 7-day constraint, making the call self-sufficient. Only minor gap is no explicit guidance on the alternative export/measurement tools.

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 coverage is 100%, so the baseline is 3, but the description adds cross-parameter meaning the schema lacks: the date window is capped at 7 days, one crop season per call is the norm, and org_id/field_id provenance is spelled out. That is real added value over the field-level descriptions.

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 ('List the field operations recorded on one field') and enumerates the operation kinds covered (tillage, seeding, application, harvest). The mention that each operation's `id` feeds jd_get_field_operation_measurements and the shapefile download cleanly separates it from those siblings.

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

Usage Guidelines4/5

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

Gives clear operational context: 'One crop season per call is the normal use', and points to jd_list_organizations and jd_list_fields for the required IDs. It does not, however, state when to prefer this over jd_export_field_operations or when a single-operation lookup (jd_get_field_operation_measurements) is the better call.

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