Skip to main content
Glama
Sign In

g4rden garden planner

by com.g4rden
OverviewDiscussionsAdmin

Get a plant's growing notes

get_plant
Read-only

How to grow a plant (vegetable, herb, fruit or flower) as Markdown: spacing, sun, water, timing relative to frost, companions and pests.

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": "get_plant"
  }
}

Input Schema

NameRequiredDescriptionDefault
plantYesA plant name, e.g. 'tomato', 'garlic', 'sweet pea'.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior4/5

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

Annotations already establish read-only and closed-world behavior. The description adds useful context by specifying the return format (Markdown) and enumerating the growing-note sections, though it does not cover error handling for unknown plant names.

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?

One front-loaded sentence with a colon-delimited list; every element describes returned content and there is no filler.

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?

For a one-parameter read-only tool with no output schema, the description adequately explains the return format and content. It could be more complete by noting behavior for unknown plant names or pointing to related tools, but the core is covered.

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% and the single parameter is documented with examples such as 'tomato', 'garlic', and 'sweet pea'. The description does not add syntax or constraints beyond the schema, so the baseline of 3 applies.

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 states the resource and the exact content returned: spacing, sun, water, frost timing, companions, and pests, plus the Markdown format. It is clear but does not distinguish this tool from siblings such as what_to_plant or get_pest.

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

Usage Guidelines2/5

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

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The content implies it is for growing instructions, but the agent must infer that from the description alone.

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 toolsInspect
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