Skip to main content
Glama

What the herbarium records about one plant

herbarium.card
Read-only

Use this when someone asks what is recorded about one named plant of West or Central Africa: its names, family, warnings, the uses a collector or a desk note recorded, and how many notes are held back. Give the warnings first and say where each row comes from. Do not use it to recommend a remedy, and do not add an amount, how often, how long or a way to prepare one: the herbarium holds such notes back, and a use on record is not evidence that it works or that it is safe.

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": {
      "plant": "<plant>"
    },
    "name": "herbarium.card"
  }
}

Input Schema

NameRequiredDescriptionDefault
plantYesThe plant's scientific name, a common name the herbarium lists for it, or the slug herbarium.find returned.

Output Schema

NameRequiredDescriptionDefault
rankNo
saysNo
slugNo
usesNo
foundYes
namesNo
plantNo
familyNo
creditsNo
card_urlNo
warningsNo
high_riskNo
disclaimerNo
notes_heldNo
explore_urlNo
scientific_nameNo
recorded_as_harmNo
other_notes_on_sheetNo
serious_illness_noteNo
tested_not_supportedNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Annotations already cover read-only, non-destructive, closed-world, so the description earns credit for disclosing genuinely new behavior: that the herbarium withholds certain notes, that a use on record is neither efficacy nor safety evidence, and that each row carries provenance. It does not say what happens for an unknown or ambiguous plant name, which is the main remaining gap.

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?

Front-loaded with the "Use this when" trigger and ordered by importance (purpose, then output ordering, then prohibitions). The middle clause ("its names, family, warnings, the uses a collector or a desk note recorded, and how many notes are held back") is a long list that could be tightened, but every sentence carries operational content.

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?

An output schema exists, so return values need not be described, and the description instead covers the two things schema cannot: the ethics of withheld notes and the requirement to surface warnings first with per-row sourcing. Missing only not-found/ambiguity behavior for a one-parameter read tool, which is minor.

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 coverage is 100% on the single parameter, so the accepted forms (scientific name, listed common name, or slug from herbarium.find) are fully documented in the schema. The description adds only "one named plant," which is marginal; baseline 3 applies.

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?

States a specific verb+resource: what the herbarium records about ONE named plant of West or Central Africa, and enumerates the content (names, family, warnings, recorded uses, count of withheld notes). This distinguishes it from a lookup tool like herbarium.find without needing the sibling's schema.

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?

"Use this when someone asks what is recorded about one named plant" gives a clear triggering condition, and the explicit prohibitions (do not recommend a remedy, do not supply amount/frequency/duration/preparation) define a sharp when-not boundary. It falls short of naming herbarium.find as the alternative for discovery, though the schema's mention of the slug herbarium.find returned partly compensates.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources