Skip to main content
Glama

About the KwekuAnansi herbarium

herbarium.about
Read-only

Use this when someone asks what the KwekuAnansi herbarium is, how many plants it holds, where its records come from or what it leaves out. Do not use it to look up a plant: use herbarium.find or herbarium.card.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
cardsYes
creditsYes
held_backYes
high_riskNo
disclaimerYes
explore_urlNo
one_speciesNo
herbarium_urlYes
does_not_coverYes
with_a_warningNo
herbarium_builtNo
community_knowledgeYes
with_a_use_on_recordNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.7/5.0
Behavior4/5

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

Annotations already declare the tool is read-only, closed-world, and non-destructive. The description adds useful behavioral scope by saying it explains what the herbarium includes and what it leaves out, though it does not elaborate further on output or limitations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two tightly written sentences: the first front-loads intended use, and the second front-loads the exclusion and alternative tools. Every sentence 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?

The tool is a zero-parameter, read-only informational endpoint with an output schema and clear annotations. The description fully covers when to call it, what it answers, and when to use siblings instead.

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?

There are zero parameters, so the baseline is 4. The description appropriately does not waste space documenting non-existent parameters.

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 informational purpose: explaining what the KwekuAnansi herbarium is, its plant count, record provenance, and exclusions. It also explicitly distinguishes this meta-information tool from sibling lookup tools herbarium.find and herbarium.card.

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 explicit when-to-use guidance covering several user question types and an explicit when-not-to-use instruction pointing to the correct alternative tools for plant lookups. No inference is needed to route between this tool and its siblings.

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