Skip to main content
Glama
Sign In
Ferret

Ferret

by ferret-project
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Search the inventory

search_inventory
Read-only

Find items by name, brand, serial number, receipt text, or meaning, see where they are kept, and check before adding items to avoid duplicates; a box QR code finds that box.

Instructions

Finds items by words (names, brands, serial numbers, text read from receipts and manuals) and by meaning ("something to make holes" finds a drill), best matches first, each with where it's kept; a box's 6-character QR label code finds the box. Start here whenever the person mentions a thing — to answer "where is…", and before create_item so you don't add a duplicate. For questions answered from documents ("what filter does the furnace take?") use ask_inventory; to browse a room, category or tag use list_items. Leaves out things that are gone or only wanted. Returns items, each with its id, fields, location path and what matched.

Input Schema

NameRequiredDescriptionDefault
limitNoHow many matches at most
queryYesWhat to look for, in the person's words: "drill", "something to make holes", a serial number or a box's label code

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.1
    • addedInput schema / properties / limit / description
      Added value: +"How many matches at most"
    • addedInput schema / properties / query / description
      Added value: +"What to look for, in the person's words: \"drill\", \"something to make holes\", a serial number or a box's label code"
  2. First observedv0.1.0

TDQS

A4.6/5.0
Behavior5/5

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

Annotations already declare readOnlyHint=true and openWorldHint=false, but the description adds substantive behavioral context: semantic matching, best-match ordering, QR-label lookup, and exclusion of gone or wanted-only items. It also describes the return shape, including each item's id, fields, location path, and what matched.

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?

The description is front-loaded with the core search behavior and then routes to alternatives. It is dense and uses several parenthetical examples, but every sentence carries useful information. Minor tightening would improve readability without losing content.

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?

There is no output schema, yet the description explains the return value well enough: items with id, fields, location path, and match information. It also covers key behavioral constraints and alternatives, making it complete for this search tool.

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 100%, so the baseline is 3 even though the description does not walk through parameters. The description adds some query semantics, such as names, brands, serial numbers, receipt text, and natural-language meaning, but most of this overlaps the schema's own examples. The limit parameter is left entirely to the schema.

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 verb and resource: finds inventory items by words or meaning, with best matches first and location included. It also distinguishes special behavior like a box's 6-character QR label code. An agent can tell exactly what this tool does without inspecting the schema.

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 explicitly says to start here whenever the person mentions a thing, to answer 'where is…', and before create_item to avoid duplicates. It also names alternatives for document questions (ask_inventory) and browsing (list_items). The when-to-use and when-not-to-use routing is complete.

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

Deploy Server

Other Tools