Skip to main content
Glama

find_plants

Read-only

Find catalog plants that match low, medium, or bright light, optionally filtering by pet-safe status and maximum price in demo credits.

Instructions

Find catalog plants for low, medium or bright light. Optionally filter by whether they are pet-safe and by a maximum price in demo credits.

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": {
      "light": "<light>"
    },
    "name": "find_plants"
  }
}

Input Schema

NameRequiredDescriptionDefault
lightYes
pet_safeNo
max_priceNo

Output Schema

NameRequiredDescriptionDefault
plantsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered structurally. The description adds that results come from a catalog and that prices are denominated in demo credits, but it says nothing about result counts, ordering, or empty-match behavior beyond what the output schema provides.

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 tight sentences with the primary scope front-loaded and the optional refinements second. Every clause carries information; only the restatement of enum values in prose is mildly redundant.

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?

This is a low-complexity read-only search with three flat parameters and an output schema that covers return values, so the description need not explain results. What remains missing - default behavior without optional filters - is minor for a tool of this shape.

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 description coverage is 0%, so the description must compensate. It clarifies max_price as an upper bound expressed in 'demo credits' - genuinely useful unit information the schema lacks - and names pet_safe as a 'pet-safe' filter, but it merely repeats the light enum values and never explains behavior when filters are absent.

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 opens with a specific verb and resource ('Find catalog plants') and scopes it to the three light levels. It is unambiguous against the sibling tools, which all concern orders, returns, and help articles, but the differentiation is incidental rather than stated.

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?

'Optionally filter by...' signals that pet_safe and max_price are refinements rather than requirements, which is useful context. However, there is no guidance on when to prefer this tool over another, no mention of what happens if the optional filters are omitted, and no exclusions.

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