Skip to main content
Glama

ForthClear Liquidation Marketplace

Search inventory

search_inventory
Read-only

Keyword search of published, in-stock surplus listings. No sign-in required. query matches the name, description, brand, SKU, and category words, in any order. If the whole query is a category (electronics, clothes, home goods), it is treated as that category filter. Pass category as a catalogue category, such as electronics or home_goods, when you want to limit results. max_price is the maximum unit price in cents. condition is salvage, customer_returns, shelf_pulls, overstock, or new_or_refurbished. Name, brand, and SKU matches rank above description matches. For a sentence about what you want, use search_inventory_semantic.

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

Input Schema

NameRequiredDescriptionDefault
qNoAlias for query.
limitNoMaximum listings to return (default 20, max 100).
queryNoWords to match, or a category name such as electronics or clothes. Not a sentence — use search_inventory_semantic for that. `q` is accepted as an alias.
categoryNoLimit to one catalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other. Prose such as "Electronics" or "clothes" is accepted and mapped to the stored value.
conditionNoCondition of the goods: salvage (sold as-is), customer returns, shelf pulls, overstock, or new or refurbished.
max_priceNoMaximum unit price in cents. 5000 means $50.00.

Output Schema

NameRequiredDescriptionDefault
totalYesCatalogue matches before the limit is applied.
messageYes
productsYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "Alias for query.",
      +  "type": "string"
      +}
    • changedInput schema / properties / query / description
      Previous value: -"Words to match, or a category name such as electronics or clothes. Not a sentence — use search_inventory_semantic for that."New value: +"Words to match, or a category name such as electronics or clothes. Not a sentence — use search_inventory_semantic for that. `q` is accepted as an alias."
  2. Changed10 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Limit to one catalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other."New value: +"Limit to one catalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other. Prose such as \"Electronics\" or \"clothes\" is accepted and mapped to the stored value."
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "electronics",
      +  "apparel",
      +  "home_goods",
      +  "beauty",
      +  "sports",
      +  "kitchenware",
      +  "office_supplies",
      +  "toys",
      +  "food_beverage",
      +  "tools",
      +  "other"
      +]
    • addedOutput schema / properties / products / items / properties / instant_checkout_eligible
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / products / items / properties / moq
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / products / items / properties / next_step
      Added value: +{
      +  "type": "string"
      +}
    • addedOutput schema / properties / products / items / properties / quote_threshold
      Added value: +{
      +  "type": "integer"
      +}
    • addedOutput schema / properties / products / items / properties / requires_verified_reseller
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / products / items / properties / ship_from_country
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / products / items / properties / shipping_price
      Added value: +{
      +  "description": "Per-unit shipping as a number, or the string quote shipping.",
      +  "type": [
      +    "number",
      +    "string"
      +  ]
      +}
    • addedOutput schema / properties / products / items / properties / supplier
      Added value: +{
      +  "description": "Present when this listing's seller has claimed a published supplier profile.",
      +  "properties": {
      +    "country": {
      +      "type": "string"
      +    },
      +    "name": {
      +      "type": "string"
      +    },
      +    "slug": {
      +      "type": "string"
      +    },
      +    "type": {
      +      "type": "string"
      +    },
      +    "url": {
      +      "type": "string"
      +    }
      +  },
      +  "required": [
      +    "name",
      +    "slug",
      +    "country",
      +    "type",
      +    "url"
      +  ],
      +  "type": "object"
      +}
  3. Changed1 schema field changed
    • removedInput schema / properties / category / enum
      Removed value: -[
      -  "electronics",
      -  "apparel",
      -  "home_goods",
      -  "beauty",
      -  "sports",
      -  "kitchenware",
      -  "office_supplies",
      -  "toys",
      -  "food_beverage",
      -  "tools",
      -  "other"
      -]
  4. Changed4 schema fields changed
    • changedInput schema / properties / category / description
      Previous value: -"Product category"New value: +"Limit to one catalogue category. One of: electronics, apparel, home_goods, beauty, sports, kitchenware, office_supplies, toys, food_beverage, tools, other."
    • addedInput schema / properties / category / enum
      Added value: +[
      +  "electronics",
      +  "apparel",
      +  "home_goods",
      +  "beauty",
      +  "sports",
      +  "kitchenware",
      +  "office_supplies",
      +  "toys",
      +  "food_beverage",
      +  "tools",
      +  "other"
      +]
    • changedInput schema / properties / max_price / description
      Previous value: -"Maximum price in cents"New value: +"Maximum unit price in cents. 5000 means $50.00."
    • changedInput schema / properties / query / description
      Previous value: -"Search query"New value: +"Words to match, or a category name such as electronics or clothes. Not a sentence — use search_inventory_semantic for that."
  5. Changed5 schema fields changed
    • changedInput schema / properties / condition / description
      Previous value: -"Standard liquidation condition grade (Task #72)"New value: +"Condition of the goods: salvage (sold as-is), customer returns, shelf pulls, overstock, or new or refurbished."
    • addedOutput schema / properties / products / items / properties / description
      Added value: +{
      +  "description": "Plain-text listing copy. HTML and citation markers are removed.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / products / items / properties / image_url
      Added value: +{
      +  "description": "Absolute https URL of the primary photo, or null when the listing has none.",
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / products / items / properties / url
      Added value: +{
      +  "description": "Absolute URL of the public listing page.",
      +  "type": "string"
      +}
    • changedOutput schema / properties / products / items / required
      Previous value: -[
      -  "id",
      -  "name",
      -  "category",
      -  "quantity",
      -  "price"
      -]New value: +[
      +  "id",
      +  "name",
      +  "category",
      +  "quantity",
      +  "price",
      +  "url"
      +]
  6. Changed3 schema fields changed
    • addedInput schema / properties / limit / description
      Added value: +"Maximum listings to return (default 20, max 100)."
    • removedInput schema / properties / min_discount
      Removed value: -{
      -  "maximum": 100,
      -  "minimum": 0,
      -  "type": "integer"
      -}
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "properties": {
      +    "message": {
      +      "type": "string"
      +    },
      +    "products": {
      +      "items": {
      +        "properties": {
      +          "category": {
      +            "type": "string"
      +          },
      +          "condition": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "discount_percent": {
      +            "description": "Null when the listing has no original retail price on file.",
      +            "type": [
      +              "integer",
      +              "null"
      +            ]
      +          },
      +          "id": {
      +            "description": "Opaque listing id, `product_<n>`.",
      +            "type": "string"
      +          },
      +          "name": {
      +            "type": "string"
      +          },
      +          "price": {
      +            "description": "Unit price in cents.",
      +            "type": "integer"
      +          },
      +          "quantity": {
      +            "type": "integer"
      +          }
      +        },
      +        "required": [
      +          "id",
      +          "name",
      +          "category",
      +          "quantity",
      +          "price"
      +        ],
      +        "type": "object"
      +      },
      +      "type": "array"
      +    },
      +    "total": {
      +      "description": "Catalogue matches before the limit is applied.",
      +      "type": "integer"
      +    }
      +  },
      +  "required": [
      +    "products",
      +    "total",
      +    "message"
      +  ],
      +  "type": "object"
      +}
  7. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds genuine context beyond that: no sign-in required, only published and in-stock listings are in scope, and name/brand/SKU matches rank above description matches. It does not mention result paging behavior, but `limit` is fully documented in the schema.

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?

Front-loaded with the core purpose, then progressively narrower detail, and the alternative-tool pointer is placed last as a routing cue. A few sentences duplicate enum and unit details already in the schema, which is the only waste.

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 an output schema present, return values need no explanation, and the description covers the remaining agent questions: matching rules, ranking, category coercion, authentication needs, and the semantic alternative. Nothing required to call this correctly is missing.

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; the description exceeds it by explaining matching semantics the schema omits — that `query` matches name, description, brand, SKU and category words in any order, and that a whole-query category is treated as a filter. The restatements of max_price units and condition values duplicate the schema but are harmless.

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 opening sentence gives a specific verb (keyword search) plus resource (published, in-stock surplus listings) and scope constraints. It also explicitly distinguishes itself from the semantic sibling, so an agent can route between the two without opening either 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?

The description states when to use this tool and names the exact alternative: 'For a sentence about what you want, use search_inventory_semantic.' It further clarifies that a whole-query category name is auto-treated as a category filter, which pre-empts a common misuse.

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