Kindwise Identification

Diagnose crop

diagnose_crop

Pass images as public https URLs (Kindwise product servers download; this proxy does not fetch) or as base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg"]}. Use that URL only if you have no user photo; then say so. Do not invent URLs. Wikimedia often returns HTTP 424; retry with base64. Diagnose crop diseases, disorders, and pests from field photographs using Kindwise Crop.health. Use for agricultural crops (not ornamental houseplants) when the user wants likely pathogens, pests, symptoms, severity, and treatment notes. Include close-ups of lesions plus a wider canopy shot when possible. Optional latitude and longitude improve regional ranking. Returns crop and disease/pest suggestions with the requested detail fields. Creates a Kindwise identification and counts against the per-IP trial quota (default 10 calls per rolling 24 hours). No client API key is required or accepted. Treatment fields are informational; they are not a substitute for a local agronomist or pesticide label. When you are done with this trial, call submit_feedback in English about the service — not about a single diagnosis.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`images`	No	Public https URLs (Kindwise product servers download; this proxy does not fetch) or base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {"images":["https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg"]}. Use that URL only if you have no user photo, and tell the user it is the Kindwise trial photo.
`details`	No	Comma-separated extra fields to include on each suggestion. Allowed tokens: type, common_names, wiki_description, description, treatment, symptoms, severity, spreading. Unknown tokens are ignored by upstream.	type,common_names,wiki_description,description,treatment,symptoms,severity,spreading
`language`	No	BCP 47 language for localized details such as common names (default en).	en
`latitude`	No	WGS-84 latitude of where the photo was taken. Improves wild-species ranking.
`longitude`	No	WGS-84 longitude of where the photo was taken. Provide together with latitude.
`similar_images`	No	If true, each suggestion includes visually similar reference images. Defaults to false so MCP responses stay small. Set true only if you need those URLs.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 10, 2026

changedInput schema / properties / images / description

Previous value: -"Photos as a JSON array of strings, or a single string. Call this tool even if you only have a URL or the working trial photo — chat attachments are invisible here. Each string is either (1) a public http(s) URL — Kindwise product servers download it; this proxy only forwards the URL — or (2) base64 JPEG/PNG/WebP. Do not invent URLs. Do not send localhost, file://, or login-walled URLs. Wikimedia often returns HTTP 424; then use base64. Working trial photo: [\"https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg\"]."New value: +"Public https URLs (Kindwise product servers download; this proxy does not fetch) or base64 JPEG/PNG/WebP. Chat attachments are invisible. Example: {\"images\":[\"https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg\"]}. Use that URL only if you have no user photo, and tell the user it is the Kindwise trial photo."

Changed8 schema fields changedSep 2, 2026

addedInput schema / properties / images / anyOf

Added value: +[
+  {
+    "items": {
+      "description": "Public http(s) image URL that Kindwise product servers will download, or a base64-encoded JPEG/PNG/WebP string (optional data: URL prefix). This MCP proxy does not fetch the file.",
+      "maxLength": 8000000,
+      "minLength": 1,
+      "type": "string"
+    },
+    "type": "array"
+  },
+  {
+    "type": "null"
+  }
+]

addedInput schema / properties / images / default
```
Added value: +null
```

changedInput schema / properties / images / description

Previous value: -"Required. One to eight photos as a JSON array of strings, or a single string. Each string is either (1) a public http(s) URL — Kindwise product servers download it; this proxy only forwards the URL — or (2) base64 JPEG/PNG/WebP. Chat attachments are invisible unless you copy a URL or bytes here. Do not invent URLs. Do not send localhost, file://, or login-walled URLs. Wikimedia often returns HTTP 424; then use base64. Working trial photo: [\"https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg\"]."New value: +"Photos as a JSON array of strings, or a single string. Call this tool even if you only have a URL or the working trial photo — chat attachments are invisible here. Each string is either (1) a public http(s) URL — Kindwise product servers download it; this proxy only forwards the URL — or (2) base64 JPEG/PNG/WebP. Do not invent URLs. Do not send localhost, file://, or login-walled URLs. Wikimedia often returns HTTP 424; then use base64. Working trial photo: [\"https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg\"]."

removedInput schema / properties / images / items

Removed value: -{
-  "description": "Public http(s) image URL that Kindwise product servers will download, or a base64-encoded JPEG/PNG/WebP string (optional data: URL prefix). This MCP proxy does not fetch the file.",
-  "maxLength": 8000000,
-  "minLength": 1,
-  "type": "string"
-}

addedInput schema / properties / images / maxLength
```
Added value: +8
```
addedInput schema / properties / images / minLength
```
Added value: +1
```
removedInput schema / properties / images / type
```
Removed value: -"array"
```
removedInput schema / required
```
Removed value: -[
-  "images"
-]
```

Changed3 schema fields changedSep 2, 2026

changedInput schema / properties / images / description

Previous value: -"One to eight photos. A JSON array of public http(s) URLs or base64 JPEG/PNG/WebP, or a single string. Prefer two or three sharp close-ups. This server cannot see chat attachments unless you copy bytes or a fetchable URL here. Do not send localhost, file://, or authenticated URLs. Wikimedia often fails with HTTP 424; use base64 in that case."New value: +"Required. One to eight photos as a JSON array of strings, or a single string. Each string is either (1) a public http(s) URL — Kindwise product servers download it; this proxy only forwards the URL — or (2) base64 JPEG/PNG/WebP. Chat attachments are invisible unless you copy a URL or bytes here. Do not invent URLs. Do not send localhost, file://, or login-walled URLs. Wikimedia often returns HTTP 424; then use base64. Working trial photo: [\"https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg\"]."

changedInput schema / properties / images / examples

Previous value: -[
-  [
-    "https://images.example.com/leaf.jpg"
-  ]
-]New value: +[
+  [
+    "https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg"
+  ]
+]

changedInput schema / properties / images / items / description

Previous value: -"Public http(s) image URL Kindwise can fetch, or a base64-encoded JPEG/PNG/WebP string (optional data: URL prefix)."New value: +"Public http(s) image URL that Kindwise product servers will download, or a base64-encoded JPEG/PNG/WebP string (optional data: URL prefix). This MCP proxy does not fetch the file."

First observedSep 1, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Even beyond the annotations, the description reveals critical behavior: the MCP proxy does not fetch URLs, chat attachments are invisible, the service creates a Kindwise identification and counts against a per-IP quota, no API key is required or accepted, and treatment fields are informational only. It also warns about Wikimedia 424 errors. This is far more than annotations convey, directly guiding agent expectations.

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?

The description is long and information-dense, but nearly every sentence carries a distinct, useful fact (URL behavior, base64 option, quota, no API key, removable disclaimer, feedback request). It front-loads the critical transport constraints and scopes the purpose clearly. It is not verbose in a wasteful way, though it could be tightened without losing much.

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?

For a tool with no output schema and 6 parameters, the description covers input transport, location hints, quota limits, regional ranking, and informs the agent what the response contains ('crop and disease/pest suggestions with the requested detail fields'). It lacks a citation of return value structure, but given the complexity and the absence of an output schema, it is more complete than most descriptions.

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 the baseline is 3. The description adds genuine value beyond the schema: it warns against inventing URLs, explains when to use the example URL, recommends including close-ups and a canopy shot, says latitude/longitude improve ranking, and notes unknown details tokens are ignored. These enrich the parameter meaning substantially.

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?

The description opens with a specific action on a resource: 'Diagnose crop diseases, disorders, and pests from field photographs using Kindwise Crop.health.' It further scopes to agricultural crops (not ornamental houseplants), which differentiates it from the sibling identify_plant and identify_insect. This is a clear, non-tautological purpose that an agent can act on.

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?

It explicitly says to use the tool 'for agricultural crops (not ornamental houseplants) when the user wants likely pathogens, pests, symptoms, severity, and treatment notes.' This gives a strong when/when-not signal. It also instructs when to use the example URL and when to fall back to base64, and directs the agent to call submit_feedback after the trial. It does not formally name the alternates like identify_plant, but the scope boundary is clear enough.

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

All Kindwise Identification tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?