Kindwise Identification

Identify plant

identify_plant

Call this tool. Do not skip it because the user attached a photo in chat — attachments are invisible here. Pass images as public http(s) URLs (Kindwise product servers download them; this MCP proxy does not fetch the file) or as base64 JPEG/PNG/WebP. If you have no user photo yet, call with the working trial photo: https://cdn.prod.website-files.com/64876ae345f1e27598fafc02/6a9685b0fb44053ea552bedc_plant.jpg. Do not invent URLs. If a URL returns HTTP 424, retry with base64. Omit similar_images unless you need it true. 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	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"].
`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. Dates show when Glama detected each change.

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

Behavior5/5

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

Even though annotations already mark this as non-read-only, the description adds substantial behavioral context: it creates a Kindwise identification, counts against a per-IP trial quota, requires no client API key, has the Kindwise servers download URLs rather than the proxy fetching files, and warns that results are not medical/legal/foraging advice. It also discloses HTTP 424 retry behavior. This far exceeds what annotations provide.

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 but information-dense, with critical guidance front-loaded ('Call this tool. Do not skip it...'). Some redundancy exists, such as repeating the trial photo URL and the base64 vs URL distinction both in prose and in the schema. However, nearly every sentence carries operational value, so the length is justified overall.

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?

For a tool with 8 parameters, no output schema, and several operational pitfalls, the description is remarkably complete. It covers input formats, quota and auth, retry behavior, photo quality guidance, optional geolocation, health assessment semantics, return shape ('ranked taxon suggestions with probabilities plus the requested detail fields'), and safety limitations. There is no obvious missing detail an agent would need to invoke it correctly.

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?

Schema coverage is 100%, so the baseline would be 3, but the description adds rich meaning beyond the schema: how to pass images (public http(s) URLs vs base64 JPEG/PNG/WebP), not to invent URLs, the working trial photo, the 424 retry fallback, when to set health to auto/all/only, and that similar_images should be omitted unless needed. This materially improves an agent's ability to set parameters correctly.

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 distinguishes from sibling tools by limiting scope to vascular plants (houseplants, trees, wildflowers, grass, crops, weeds) versus insects, mushrooms, or crop-specific diagnosis. The purpose is unambiguous and actionable.

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?

The description gives explicit when-to-use guidance ('Use when the user supplies a photo... and needs scientific name, common names, taxonomy'), and includes a critical exclusion: 'Do not skip it because the user attached a photo in chat — attachments are invisible here.' It also provides a fallback trial photo and workflow direction to submit_feedback after the trial, which is clearer than most tool definitions.

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

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

A4.5/5.0

Disambiguation4/5

The four identification tools are clearly partitioned by target organism or purpose: plant, insect, mushroom, and crop disease. There is minor potential overlap between identify_plant with health assessment and diagnose_crop, but the descriptions clarify the intended distinction.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern: identify_plant, identify_insect, identify_mushroom, diagnose_crop, submit_feedback. The naming is predictable and makes each tool's purpose immediately clear.

Tool Count5/5

Five tools is appropriately scoped for a focused identification service. Each tool covers a distinct identification category plus a feedback mechanism, with no redundant or unnecessary entries.

Completeness4/5

The toolbox covers the core identification workflows: plants, insects, mushrooms, and crop diseases, plus user feedback. A minor gap is the lack of explicit result retrieval or broader organism identification, but this is not a significant limitation for the stated trial scope.

Resources

Need Help?