Skip to main content
Glama

Search products

search_products

Search the x402 Forge tool shop by keywords. Returns each tool's slug, a plain summary, whether it is still for sale, and its buy URL.

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": {
      "query": "<query>"
    },
    "name": "search_products"
  }
}

Input Schema

NameRequiredDescriptionDefault
queryYesKeywords, e.g. 'iban' or 'working days'

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.8/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the response fields (slug, summary, for-sale flag, buy URL), which is real value, but says nothing about matching behavior (substring vs. semantic), empty-result handling, result limits, pagination, or whether any ranking is applied.

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 short sentences, front-loaded with the action and followed by the return shape. No filler, though the return-field enumeration could be tightened into a single clause.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a one-parameter read tool this is close to adequate, and the enumerated return fields compensate for the absent output schema. However, with zero annotations the description should at minimum confirm this is a read-only, side-effect-free lookup and indicate how many results to expect.

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% and there is only one required parameter, whose schema description already gives examples ('iban', 'working days'). The description reinforces that the parameter is a keyword query rather than a filter object, adding modest value on top of an already self-documenting 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?

States a specific verb and resource ('Search the x402 Forge tool shop') plus the match mechanism ('by keywords'), and the return payload is enumerated. The agent can distinguish it from buy_product, describe_product, or order_product because the description frames this as discovery rather than transaction.

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?

The word 'search' plus the keyword input implies discovery-before-purchase usage, and the sibling set makes the shopping flow apparent, but the description never explicitly says when to use this rather than describe_product or suggest_tool. No exclusions or prerequisites are stated, leaving routing to inference.

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