Kindwise Identification

Identify plant

identify_plant

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. Identify a vascular plant from photographs using Kindwise Plant.id. Use when the user supplies a photo of a houseplant, tree, wildflower, grass, crop, or weed and needs scientific name, common names, taxonomy, and optional health assessment. Prefer 2–3 sharp close-ups of leaves, flowers, or fruit. Optional latitude and longitude improve ranking for wild plants. Returns ranked taxon suggestions with probabilities plus 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. Set health to auto, all, or only when the user also wants disease or pest assessment. Do not treat results as medical, legal, or foraging advice. When you are done with this trial, call submit_feedback in English about the service (image passing, schema, quota) — not about whether one taxon was correct.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`health`	No	Optional plant-health assessment. `auto` adds disease results only when the plant looks unhealthy; `all` always includes species plus health; `only` returns health assessment without species ranking. Omit for species identification alone.
`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: common_names, url, description, taxonomy, rank, name_authority, gbif_id, inaturalist_id, image, images, synonyms, edible_parts, propagation_methods, watering. Unknown tokens are ignored by upstream.	common_names,url,description,taxonomy,rank,edible_parts,watering
`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.
`classification_level`	No	Taxonomic rank of suggestions: `species` (default upstream behavior), `genus`, or `all` (genus, species, and infraspecies).

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

Behavior5/5

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

The description discloses substantial behavioral detail beyond the annotations: the proxy does not fetch URLs, chat attachments are invisible, Wikimedia URLs often return HTTP 424, calls count against a per-IP trial quota, no API key is required or accepted, and results should not be treated as medical/legal/foraging advice. It also confirms the operation creates a Kindwise identification, consistent with readOnlyHint=false.

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 dense and front-loaded with the most critical information (image passing format), followed by usage context and operational constraints. It is long but nearly every sentence carries actionable guidance; a slight structural improvement would be breaking it into scannable sentencs or sections.

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 8 parameters, minimal annotations, and no output schema, the description covers the essential operational picture: input formats, limitations, quota, no-key auth, output shape ('ranked taxon suggestions with probabilities plus the requested detail fields'), and follow-up feedback routing. Nothing needed to invoke the tool correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Although schema coverage is 100%, the description adds critical semantics: base64 vs public URL handling, the example trial URL and instruction to disclose its use, 'Do not invent URLs', retry with base64 on Wikimedia 424, photo quality guidance (2–3 sharp close-ups), and when health values auto/all/only are appropriate. This goes well beyond the schema's field descriptions.

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 states a specific verb and resource: 'Identify a vascular plant from photographs using Kindwise Plant.id.' It clearly differentiates from sibling tools by naming the domain (houseplants, trees, wildflowers, grass, crops, weeds) and the expected output (scientific name, common names, taxonomy, optional health assessment).

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?

The description gives explicit when-to-use guidance: 'Use when the user supplies a photo of a houseplant, tree, wildflower, grass, crop, or weed...' It also advises on photo selection, optional latitude/longitude, and when to enable health assessment. It does not explicitly name sibling alternatives such as diagnose_crop, but the context is clear enough to route the agent correctly.

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?