Deere Ops Center MCP

Overview Schema Source Related Servers Discussions Admin

jd_list_products

Read-only

List products of a single type—chemicals, fertilizers, seed varieties, tank mixes, or dry blends—for a John Deere organization to view what is defined and available.

Instructions

List one kind of product defined in an organization.

    Returns `products`, each with `id`, `name`, `category`, `type`, `cropName`,
    `companyName`, `archived` and `uri`. One call lists one `product_type`: chemicals,
    fertilizers, seed varieties, tank mixes or dry blends. Get `org_id` from
    jd_list_organizations. Use it to see what the organization has defined, for example
    which seed varieties or chemicals exist.

Input Schema

TableJSON Schema

Name	Required	Description
`org_id`	Yes	Organization ID from jd_list_organizations.
`status`	No	Filter by availability. Omit for Deere's default.
`product_type`	Yes	Which kind of product to list.

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.1/5.0

Behavior4/5

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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description still adds genuinely useful behavior beyond that: one call returns only one product_type, the returned field set is enumerated, and it tells the agent where org_id must come from.

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 in the first sentence, then scope, then provenance. Slightly wasteful: it enumerates return fields even though an output schema exists, which is redundant real estate.

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?

Given an output schema exists and 100% parameter coverage in the schema, the description needs only the action, the one-type-per-call constraint and org_id provenance — all present. Minor gap: nothing notes pagination or result-size behavior for large organizations.

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 baseline is 3 by rule. The description restates the five product_type kinds in prose (mapping to the enum) and the org_id provenance, but adds no syntax or format detail the schema does not already carry.

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 one kind of product defined in an organization') and immediately constrains scope to a single product_type per call, enumerating the five kinds. An agent can distinguish this from jd_list_fields, jd_list_operators, etc., without opening the schema.

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 context: use it to see what an organization has defined, e.g. which seed varieties or chemicals exist, and directs the agent to jd_list_organizations for org_id. No explicit when-not or alternative tool for product discovery is named, so it stops short of a 5.

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