Deere Ops Center MCP

Overview Schema Source Related Servers Discussions Admin

jd_get_machine_alerts

Read-only

Fetch machine alerts and diagnostic trouble codes for one John Deere machine using its principal ID and a date range, with an option to exclude acknowledged alerts.

Instructions

Get machine alerts (diagnostic trouble codes) for one machine.

    Returns the alerts under 'alerts'. `principal_id` comes from jd_list_equipment. Deere
    allows at most 7 days between start_date and end_date in a single request; ask for a
    shorter window or make several calls.

Input Schema

TableJSON Schema

Name	Required	Description
`end_date`	No	End of the window, ISO 8601 UTC, e.g. 2026-10-07T00:00:00Z.
`start_date`	No	Start of the window, ISO 8601 UTC, e.g. 2026-10-01T00:00:00Z.
`principal_id`	Yes	Machine principal ID: the 'principalId' of an item from jd_list_equipment.
`exclude_acknowledged`	No	True to leave out alerts the operator already acknowledged.

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 already cover the safety profile (readOnlyHint=true, openWorldHint=true), so the bar is lower. The description adds real value beyond them: it discloses the return key ('alerts') and the hard 7-day span constraint imposed by Deere plus the recommended workaround, which an agent could not infer from the schema.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Three tight sentences, front-loaded with purpose, then provenance, then the operational constraint. No filler; the awkward indentation is cosmetic rather than wasteful.

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?

With an output schema present, return values need not be spelled out, and the description still names the payload key. Provenance of the required ID and the request-window constraint are both covered, so an agent has everything needed to call this correctly for a 4-parameter tool.

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 schema already documents all four parameters, including principal_id's provenance and the ISO 8601 format for the dates. The description only restates principal_id's origin and relates the 7-day constraint to the date range, adding marginal meaning beyond structured data. Baseline 3 is appropriate.

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?

Starts with a specific verb+resource ('Get machine alerts') and immediately disambiguates the term with '(diagnostic trouble codes) for one machine'. An agent can distinguish this from the equipment-related siblings (jd_list_equipment, jd_get_machine_engine_hours, 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 operational context: principal_id is sourced from jd_list_equipment, and the 7-day window rule tells the agent when to split requests. It stops short of explicitly naming an alternative tool or stating when NOT to use this one, so it doesn't reach a 5.

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