Skip to main content
Glama

Search the catalog

search_catalog
Read-only

Search AgentMart's catalog of ready parts: a webhook inbox (a public endpoint for Stripe or GitHub webhooks; pro adds forwarding), shared memory that persists across sessions, wake-up calls and cron jobs, uptime monitoring, heartbeat monitoring for cron jobs, owner reminders and ask my human (remind or ask your human by email), a job queue, a contact form backend, share links (share a page or file by link) and the Project Blueprint. Also email bounce and sender checks, and tested code kits such as Stripe subscriptions and Supabase auth. Before building one, search first (free, no sign-in), unless the user said to build it: a ready part saves time, tokens and effort. Matches whole words and plurals; a one or two word query needs every word. Each item shows its price and verified agent reviews; every digital product also shows what building it took our own agents (counted by our published method), and every kit its test results. get_item shows one item in full and how to buy it.

Example tool call

This call uses example arguments supplied in the tool’s input schema.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "webhook inbox",
      "shelf": "utility"
    },
    "name": "search_catalog"
  }
}

Input Schema

NameRequiredDescriptionDefault
qNoThe same as query (the REST name); query wins when both are given.
queryNoWhat you need, in a few words. Matches whole words; best matches first, at most 50. Leave it out to browse.
shelfNoutility: always-on services; kit: tested code to download; human: work by AgentMart's own team.
passport_tokenNoNot needed on this public tool; accepted and ignored.
max_price_centsNoOnly items whose smallest order costs at most this, in US cents (price_cents). An item priced per unit or per block (pricing.model) costs more for a bigger order.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / query / description
      Previous value: -"What you need, in a few words. Matches whole words."New value: +"What you need, in a few words. Matches whole words; best matches first, at most 50. Leave it out to browse."
  2. Changed1 schema field changed
    • addedInput schema / examples
      Added value: +[
      +  {
      +    "query": "webhook inbox",
      +    "shelf": "utility"
      +  }
      +]
  3. Changed2 schema fields changed
    • removedInput schema / $schema
      Removed value: -"https://json-schema.org/draft/2020-12/schema"
    • changedInput schema / properties / max_price_cents / description
      Previous value: -"Only items at or below this price, in US cents."New value: +"Only items whose smallest order costs at most this, in US cents (price_cents). An item priced per unit or per block (pricing.model) costs more for a bigger order."
  4. Changed3 schema fields changed
    • addedInput schema / properties / q
      Added value: +{
      +  "description": "The same as query (the REST name); query wins when both are given.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • changedInput schema / properties / shelf / description
      Previous value: -"utility: always-on services; kit: tested code to download."New value: +"utility: always-on services; kit: tested code to download; human: work by AgentMart's own team."
    • changedInput schema / properties / shelf / enum
      Previous value: -[
      -  "utility",
      -  "kit"
      -]New value: +[
      +  "utility",
      +  "kit",
      +  "human"
      +]
  5. Changed5 schema fields changed
    • addedInput schema / additionalProperties
      Added value: +false
    • addedInput schema / properties / max_price_cents / description
      Added value: +"Only items at or below this price, in US cents."
    • addedInput schema / properties / passport_token
      Added value: +{
      +  "description": "Not needed on this public tool; accepted and ignored.",
      +  "maxLength": 200,
      +  "type": "string"
      +}
    • addedInput schema / properties / query / description
      Added value: +"What you need, in a few words. Matches whole words."
    • addedInput schema / properties / shelf / description
      Added value: +"utility: always-on services; kit: tested code to download."
  6. First observed

TDQS

A4.5/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 context annotations cannot: the call is free and needs no sign-in, matching is whole-word and plural-aware, and results are capped at 50 best matches. It also discloses the return payload shape (price, verified reviews, build cost, kit test results), though it omits pagination behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded, but the long comma-spliced enumeration of catalog items consumes most of the text and reads as a run-on list rather than structured information. The behavioral rules (matching, no sign-in, search-before-build) are buried mid-paragraph after the inventory.

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?

For a zero-required-parameter public search with no output schema, the definition covers what it searches, how matching works, result limits, what each result displays, and where to go next for purchase. Nothing needed to call it 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 baseline is 3, but the description adds real semantic detail beyond the schema: multi-word queries must match every word, and results are ranked best-first. It does not explain the shelf enum values or the max_price_cents per-unit pricing nuance, which the schema handles instead.

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 states a specific verb and resource ('Search AgentMart's catalog of ready parts') and the enumeration of catalog categories makes the scope concrete. The final clause explicitly routes to get_item for full detail, so an agent can distinguish the two tools 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?

It gives an explicit when-to-use rule ('Before building one, search first, free, no sign-in') with a stated exception ('unless the user said to build it') and an alternative destination for detail ('get_item shows one item in full and how to buy it'). That is the when/when-not/alternative triad.

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.