Kindwise Identification

Identify insect

identify_insect

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. Pass 1–8 images as public http(s) URLs or base64-encoded JPEG/PNG/WebP; 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`	Yes	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.
`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.

TDQS

A4.5/5.0

Behavior5/5

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

Discloses that it creates a Kindwise identification, counts against a per-IP trial quota (default 10 calls per rolling 24 hours), requires no client API key, and results are not medical or pest-control prescriptions. This goes beyond the annotations by specifying side effects and rate limits clearly.

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 every sentence serves a purpose: purpose, usage, image requirements, optional parameters, return summary, quota, no API key, disclaimers, and feedback instruction. It is front-loaded with purpose and usage, and logically structured, though slightly verbose.

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?

Given 6 parameters, no output schema, and complex operational details (quota, no API key, side effects), the description covers all necessary aspects: input format, quota, output summary, and safety disclaimers. It indicates the return is 'ranked taxon suggestions with probabilities plus requested details,' which is sufficient for an agent to understand the result type.

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?

The input schema provides 100% coverage of all parameters with detailed descriptions (e.g., images format, details tokens, language pattern, lat/long ranges). The description adds minor advice like 'prefer a sharp dorsal or lateral view' for image quality, but largely restates schema content. Baseline of 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 clearly states it identifies insects and insect-like arthropods from photos, listing specific examples like beetle, moth, bee, ant, true bug, and spider-like pest. It distinguishes from sibling identification tools by focusing on the invertebrate group, making the purpose unambiguous.

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?

Explicitly states when to use ('Use when the user supplies a photo of a beetle...'), provides image format requirements (public URLs or base64, sharp dorsal/lateral view), optional lat/long, and even instructs to call submit_feedback after the trial. It also notes that results are not prescriptions, giving clear context for appropriate use.

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

Disambiguation5/5

Each identification tool targets a distinct organism group (plant, insect, mushroom) and diagnose_crop is clearly separate for crop health issues. submit_feedback is unambiguous as a meta-tool. No two tools appear interchangeable.

Naming Consistency4/5

Most tools follow a clear identify_<organism> pattern, with diagnose_crop as a meaningful exception that reflects its different purpose. submit_feedback also fits the verb_noun convention, so the overall pattern is consistent with only a minor deviation.

Tool Count5/5

Five tools is a well-scoped set for a species-identification service: four domain tools covering the main organism categories plus one feedback tool. Each tool has a clear, non-redundant role.

Completeness4/5

The surface covers the core identification needs for plants, insects, mushrooms, and crop diseases, plus feedback for the trial. A minor gap is the lack of any retrieval/history mechanism, but it is not essential for the stated trial purpose.

Resources

Need Help?