Kweku Anansi Herbarium

Find a plant in the Kweku Anansi herbarium

herbarium.find

Read-only

Use this when someone names a plant of West or Central Africa by its scientific name or a common name (for example "Azadirachta indica", "sobolo" or "prekese") and you need to know whether the Kweku Anansi herbarium has a card for it. It returns the matching cards with family and rank, and says plainly when a plant is not in the herbarium yet. Do not use it to identify a plant from a description or a photograph, or for a plant from outside Africa: it matches names as written, and a plant that is not found may be there under another name.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "name": "<name>"
    },
    "name": "herbarium.find"
  }
}

Input Schema

Name	Required	Description	Default
`name`	Yes	The plant's scientific name ("Vernonia amygdalina") or a common name ("bitter leaf").

Output Schema

Name	Required	Description	Default
`name`	Yes
`says`	Yes
`matched`	Yes
`matches`	Yes
`flags_note`	No
`explore_url`	No
`herbarium_built`	No
`cards_in_herbarium`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 11, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare this a safe, closed-world read, so the marginal burden is low. The description adds value beyond them: it says results include family and rank, that a negative answer is reported plainly, and that name matching is exact — a failure-mode disclosure an agent cannot infer from structured fields.

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?

Two sentences, front-loaded with the trigger and closed with exclusions and a caveat, with no filler. The second sentence packs three separate constraints into one long clause, which is dense but every element earns its place.

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?

One required parameter, full schema coverage, annotations supplying the safety profile, and an output schema covering the return shape — so the description only needs the trigger, the scope limits, and the matching caveat, all of which are present. Nothing an agent needs to call it correctly is missing.

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

Parameters4/5

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

The schema already documents the single 'name' parameter at 100% coverage, but the description adds real meaning: both scientific and common names are accepted (with 'sobolo'/'prekese' style examples) and matching is literal 'as written', so a miss may mean an alternate name rather than absence. That changes how an agent should interpret and retry a search.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description names a specific verb ('find'), a concrete resource ('a plant in the Kweku Anansi herbarium') and states what comes back ('matching cards with family and rank'). It doesn't explicitly route to the sibling 'herbarium.card' for card details or 'herbarium.about', so it stops short of full sibling differentiation, but the lookup framing is distinct and 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?

It gives an explicit trigger ('when someone names a plant of West or Central Africa by its scientific name or a common name') with worked examples, and explicit exclusions: not for identification from a description or photograph, and not for plants from outside Africa. That is a complete when/when-not statement leaving little to inference.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All Kweku Anansi Herbarium 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?