Skip to main content
Glama
vanantwerp

Deere Ops Center MCP

by vanantwerp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

jd_get

Read-only

Make read-only GET requests to any allowed John Deere API endpoint when no dedicated tool covers it. Use link URIs and IDs from other results to fetch fields, equipment, or images.

Instructions

Make a read-only GET request to any John Deere API endpoint.

    Use this for Deere endpoints that no dedicated tool covers; follow the `links[].uri`
    values from other results to get there, and take IDs from the list tools. Only Deere
    hosts are allowed and only GET is ever sent. JSON comes back as the parsed object (lists
    are wrapped as {"data": [...]}), images come back as an image, and any other text comes
    back as {"content_type", "text", "truncated"} cut to 20,000 characters. Pass
    accept="application/vnd.deere.axiom.v3.image+json" to fetch a measurement map image.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
urlYesAbsolute Deere URL, or a path such as /organizations/123/fields that is joined to the configured API base URL.
acceptNoAccept header to send; the Deere v3 JSON type when omitted.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.9/5.0
Behavior5/5

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

Annotations declare readOnlyHint and openWorldHint, and the description goes well beyond them: it constrains hosts and method, and details return shapes for JSON (lists wrapped as {"data": [...]}), images, and other text (truncated at 20,000 characters). It even documents the accept header needed to fetch a measurement map image.

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?

Front-loads the core purpose in the first sentence, then layers routing guidance and return-format details. Every sentence conveys actionable information with no filler.

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?

No output schema exists, so the description carries the burden and does so thoroughly by describing JSON, list, image, and text/truncation return formats. An agent has everything needed to invoke it correctly.

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 both parameters are already documented as a baseline of 3. The description adds value by explaining that `url` can be an absolute Deere URL or a path joined to the configured base, and by giving the concrete accept value for image retrieval.

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 and resource: a read-only GET request to any John Deere API endpoint. It explicitly distinguishes itself from siblings by saying to use it for Deere endpoints that no dedicated tool covers.

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

Usage Guidelines5/5

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

Gives explicit when-to-use (endpoints not covered by dedicated tools) and how to use it: follow `links[].uri` values from other results and take IDs from the list tools. It also states hard constraints (only Deere hosts, only GET is ever sent), leaving nothing to inference.

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