g4rden garden planner

Identify and treat a garden pest or disease

get_pest

Read-only

A garden pest or disease as Markdown: how to recognise it, which plants it attacks, and a treatment ladder from least to most drastic. Covers 46 common pests and diseases with treatment advice and about 390 plant-health records (host plants, where recorded, regulatory status) by common or scientific 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": {
      "pest": "<pest>"
    },
    "name": "get_pest"
  }
}

Input Schema

Name	Required	Description	Default
`pest`	Yes	A pest or disease name, e.g. 'aphids', 'powdery mildew', 'slugs', 'Popillia japonica'.

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 14, 2026

TDQS

A3.9/5.0

Behavior4/5

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

Annotations already declare this a safe local read (readOnlyHint true, openWorldHint false), so the description usefully spends its words on output shape: Markdown, fixed sections, and coverage breadth (46 pests, ~390 plant-health records). It adds that host plants, recording locations, and regulatory status are included, which the annotations cannot convey.

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 dense sentences with no filler, and the content inventory is front-loaded. The opening nominal fragment ('A garden pest or disease as Markdown') lacks a verb, making the first clause slightly less immediately scannable than it could be.

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?

With no output schema, the description takes on the job of describing the return value and does so concretely: Markdown format, section structure, and catalog scale. Combined with annotations covering safety and locality, and a fully documented single parameter, an agent has what it needs to call this correctly.

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?

Schema coverage is 100% so the baseline is 3, and the description earns the extra point by stating that the lookup accepts either common or scientific names — a rule the schema only demonstrates through examples rather than declaring outright.

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 the resource (a garden pest or disease) and enumerates the returned content: recognition guidance, attacked plants, and a least-to-most-drastic treatment ladder. It is clearly distinct from get_plant by subject matter, though it never explicitly contrasts itself with that sibling.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is implied by the title ('Identify and treat a garden pest or disease') and by the accepted naming convention, but there is no explicit when-to-use statement, no guidance on what to do if a name isn't in the 46-entry catalog, and no pointer to get_plant for the host plant itself.

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

All g4rden garden planner 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?