Skip to main content
Glama
vanantwerp

Deere Ops Center MCP

by vanantwerp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

jd_download_operation_shapefile

DestructiveIdempotent

Download a field operation's point-by-point shapefile as a zip for GIS or Python analysis. Saves it to disk and returns the file path, or reports if Deere is still preparing it.

Instructions

Download the point-by-point shapefile for one field operation and save it to disk.

    The file is a zip of ESRI shapefiles (GPS points or polygons with yield, rate, moisture
    and similar values at each location), meant for GIS software or Python. This tool saves
    the zip in the output folder and returns its path and size; it does not return the
    contents, because the files are large. Operation IDs come from
    jd_list_field_operations (only operations with shapefile_available true have one).

    Deere prepares the file in the background, so this tool may wait a little. If Deere is
    still preparing it when max_wait_seconds runs out, the result has status "preparing";
    call the tool again after retry_after_seconds. On success the status is "saved".

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
filenameNoFile name to save as, inside the output folder. Defaults to operation-<operation_id>.zip.
resolutionNoHow densely to sample the operation: per machine section, per sensor, or once per second. Omit to let Deere choose its default.
shape_typeNoGeometry to export. Omit to let Deere choose its default.
operation_idYesField operation ID, from jd_list_field_operations.
max_wait_secondsNoHow long to wait for Deere to prepare the file before giving up.

Output Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations only mark it as a non-read-only, destructive, idempotent write; the description adds the substantive behavior: the zip is written to the output folder, the tool returns path and size rather than contents because files are large, Deere prepares the file asynchronously, and the result carries status 'preparing' vs 'saved' with retry_after_seconds. That is exactly the context an agent needs to avoid mis-handling the response. No contradiction with annotations.

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 the core action and result, then the async caveat. Mostly tight, though the retry explanation is slightly repetitive ('call the tool again after retry_after_seconds' restates the status semantics).

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?

Complete for a mutation-style download tool: it covers the source of the ID, output location, absent return contents (despite an output schema), and the asynchronous preparation contract. Nothing an agent needs to invoke and interpret it correctly is missing.

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 filename/resolution/shape_type defaults are already documented. The description still adds real semantics: where operation_id comes from (jd_list_field_operations), and how max_wait_seconds interacts with the 'preparing' status and retry_after_seconds, which the schema only describes as a timeout.

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+scope: downloads the point-by-point shapefile for ONE field operation and saves it to disk. It also clarifies the payload format (zip of ESRI shapefiles with yield/rate/moisture), which separates it from generic export siblings like jd_export_field_operations and jd_save_file.

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 a clear entry condition: operation IDs come from jd_list_field_operations, and only operations with shapefile_available=true have one. It also explains the retry path when status is 'preparing'. It does not explicitly say when to prefer this over jd_export_field_operations, which is the only remaining gap.

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

Deploy Server

Other Tools