Deere Ops Center MCP

Overview Schema Source Related Servers Discussions Admin

jd_get_machine_hours_of_operation

Read-only

Retrieve machine working, idle, and transport hours over a period. Pass principal ID plus optional date range, org, or state filters to inspect equipment activity records.

Instructions

Get how long a machine was working, idle or transporting over a period.

    Returns the records under 'hours_of_operation'. `principal_id` comes from
    jd_list_equipment and `org_id` from jd_list_organizations. Use start_date and end_date
    to bound the period; the detailed_state and summarize_duration filters are passed to
    Deere unchanged.

Input Schema

TableJSON Schema

Name	Required	Description
`org_id`	No	Organization ID, from jd_list_organizations. Narrows the result to that organization.
`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.
`detailed_state`	No	Deere's detailedState filter, passed through as given.
`summarize_duration`	No	Deere's summarizeDuration option, passed through as given.

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 already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value beyond that by disclosing that detailed_state and summarize_duration are passed through to Deere unchanged (implying upstream validation and Deere-specific semantics) and that results land under 'hours_of_operation'.

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 purpose in the first sentence, followed by return container, ID provenance, and date/filter behavior. No filler sentences, though the provenance and date-window sentences could be tightened slightly.

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?

An output schema exists, so return values need not be explained, and the description still names the 'hours_of_operation' container. Combined with the annotations and full schema coverage, an agent has enough to invoke it correctly; only explicit routing against sibling machine-hour tools is missing.

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 every parameter is already documented in the schema with format details (ISO 8601 UTC examples, principalId/passthrough notes). The description largely repeats that; the cross-tool ID provenance is helpful but already present in the schema text, so baseline 3 applies.

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 (Get) and resource (machine hours of operation) and concretely defines the measurement as time spent working, idle, or transporting over a period. This distinguishes it from sibling reads like jd_get_machine_engine_hours and jd_get_machine_alerts without the agent needing to open another 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 org_id from jd_list_organizations, and start_date/end_date bound the period. It does not explicitly say when to prefer this over engine-hours or other machine reads, so it stops short of full when/when-not guidance.

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