Kindwise Identification

Identify insect

identify_insect

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 insects and insect-like arthropods from photographs using Kindwise Insect.id. Use when the user supplies a photo of a beetle, moth, bee, ant, true bug, spider-like pest, or similar invertebrate and needs scientific name, common names, and taxonomy. Prefer a sharp dorsal or lateral view. 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. Results are not medical or pest-control prescriptions. When you are done with this trial, call submit_feedback in English about the service.

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, taxonomy, rank. Unknown tokens are ignored by upstream.	common_names,url,description,taxonomy,rank
`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?

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. The description adds important behavioral context: the proxy does not fetch images, chat attachments are invisible, the call counts against a per-IP trial quota, no API key is required, and results are not medical/pest-control prescriptions. It also warns about Wikimedia HTTP 424 and suggests base64 retry. This goes well beyond the annotations.

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 but well-organized: it front-loads the critical image-format constraint, then gives usage guidance, then output and quota notes. Every sentence adds value, though it is a bit long and could be tightened.

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, the description does a good job of explaining what the response contains ('ranked taxon suggestions with probabilities plus requested details'). It also covers the trial quota, retry behavior, and the no-API-key requirement. It doesn't describe the exact response structure, but for a list-style identification tool this is acceptable.

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

Parameters3/5

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

Schema description coverage is 100%, so the schema already documents all six parameters. The description adds a concrete example URL and explains the proxy's non-fetching behavior, which is useful. However, it doesn't add much beyond the schema for details, language, latitude, longitude, or similar_images. Baseline 3 is appropriate.

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'), a resource ('insects and insect-like arthropods from photographs'), and the underlying service (Kindwise Insect.id). It also names the expected output (scientific name, common names, taxonomy) and distinguishes itself from sibling tools by naming the target taxa.

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 explicitly says when to use the tool ('when the user supplies a photo of a beetle, moth, bee, ant, true bug, spider-like pest, or similar invertebrate'), and it gives clear guidance on image format, retry behavior, and the trial quota. It also mentions the sibling submit_feedback for post-trial feedback.

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?