Skip to main content
Glama
Sign In

Latchbell

by com.latchbell
OverviewDiscussionsAdmin

Read a business’s catalog

catalog
Read-only

Use after find_businesses to see what a business sells or books, with prices and options. The owner-approved catalog: items in categories, each with a price (fixed, from, or to confirm, per unit), option groups (pick one, up to N, any; a choice may add price or time, set the price like a size, or multiply it), typed fields to ask, and fulfillment (appointment, reservation, pickup, delivery, onsite, request, elsewhere: bought on its own page, product_url). team names who can be asked for, and next says which tools complete each fulfillment. Prices from/confirm are estimates. Not live stock. For one item or a long catalog, pass query (words in its name or description) and read more with page.next_offset.

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": {
      "business": "<business>"
    },
    "name": "catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNoHow many to return (default 25, at most 100)
queryNoWords in the item's name or description, e.g. "onkyo receiver": only matching items come back
offsetNoSkip this many matches: page.next_offset from the last answer
businessYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.4/5.0
Behavior5/5

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

Annotations already declare a safe read, and the description adds substantial context beyond them: the catalog is owner-approved, prices from/confirm are estimates, it is 'Not live stock', and it enumerates the fulfillment modes and the meaning of the `team` and `next` fields. This tells the agent what the data can and cannot be trusted for.

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?

Purpose and prerequisite are front-loaded, and the dense parentheticals about price types, option-group mechanics and fulfillment each carry real meaning. The single run-on paragraph with nested parentheses makes it harder to scan than it needs to 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?

There is no output schema, so the description carries the return-value burden and does so thoroughly: item/category structure, price semantics, option groups, typed fields, fulfillment modes, and pagination via page.next_offset. An agent has everything needed to call it and interpret the result.

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 75% and already documents query, offset and limit; the description mostly restates those (query matches name/description, offset follows page.next_offset) while adding only the usage condition 'for one item or a long catalog'. The required `business` parameter gets no explanation in either place.

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?

States a specific verb and resource ('see what a business sells or books, with prices and options') and immediately scopes it as the follow-up to find_businesses, so an agent can distinguish it from sibling reads like read_business_info.

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

Usage Guidelines4/5

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

Gives explicit sequencing ('Use after find_businesses') and conditional guidance for query/offset ('For one item or a long catalog, pass query ... read more with page.next_offset'). No explicit when-not-to-use or named write alternative such as update_catalog, so it stops short of a 5.

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

All Latchbell 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