Kindwise Identification

Identify mushroom

identify_mushroom

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 mushrooms and other fungi from photographs using Kindwise Mushroom.id. Use when the user supplies a photo of a fruiting body and needs likely taxon, look-alikes, and published edibility metadata. Include cap, gills or pores, and stem when possible. Optional latitude and longitude improve ranking. Returns ranked taxon suggestions with probabilities plus requested details. 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. Edibility and psychoactive fields are informational only. Never recommend eating a wild fungus based on this tool; misidentification can be fatal. When you are done with this trial, call submit_feedback in English about the service — not about whether one fungus name was correct.

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: common_names, url, description, edibility, psychoactive, taxonomy, rank, look_alike. Unknown tokens are ignored by upstream.	common_names,url,description,edibility,psychoactive,taxonomy,rank,look_alike
`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.7/5.0

Behavior5/5

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

The description discloses the proxy does not fetch images, chat attachments are invisible, no API key is required/accepted, quota limits (10 calls per rolling 24h), retry with base64 on Wikimedia 424, and safety warnings about edibility. Annotations only state readOnlyHint=false, so the description adds substantial behavioral context beyond 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 each sentence carries essential info: input requirements, example URL, quota, safety, feedback. It is front-loaded with the critical image constraint. Slightly verbose but not wasteful.

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?

Covers return format ('ranked taxon suggestions with probabilities plus requested details'), error handling (retry base64), quota, and post-call action (submit_feedback). No output schema, so this is fully adequate for an agent to call 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 has 100% coverage for all 6 parameters, but the description adds usage guidance: explains images must be public URLs or base64 with example, details tokens, location improves ranking, similar_images default to keep responses small. This goes well beyond the schema 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 ('Identify'), resource ('mushrooms and other fungi'), and method ('from photographs using Kindwise Mushroom.id'). It clearly differentiates from siblings like identify_plant and identify_insect by focusing on fungi and fruiting bodies.

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?

Explicitly states when to use: 'Use when the user supplies a photo of a fruiting body and needs likely taxon, look-alikes, and published edibility metadata.' It also provides critical constraints on image inputs (public URLs or base64, chat attachments invisible) and post-call action (submit_feedback). It does not explicitly say when to avoid this tool in favor of a sibling, but the purpose clarity covers that gap.

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?