Skip to main content
Glama
Sign In

Paylo

by com.usepaylo
OverviewDiscussionsAdmin

search_products

Read-onlyIdempotent

Search products by query, optionally scoped to a storefront and category, with pagination.

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
pageNoResult page, starting at 1 (default 1).
limitNoResults per page (1–100, default 20).
queryYesFree text over product name and description, e.g. 'iphone 13', 'shea butter'.
categoryNoProduct category name or slug to filter by (see get_categories for a store's categories).
storefrontSlugNoLimit results to one store by its slug (from search_storefronts). Omit to search across all verified stores.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only that results are paginated and can be scoped by storefront/category; it says nothing about result ordering/relevance, default across all verified stores (only implied in schema), or total-count behavior. Helpful but not rich beyond annotations.

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

Conciseness5/5

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

A single front-loaded sentence with zero filler; the core action comes first and the optional scoping and pagination follow. Nothing is redundant or buried.

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?

This is a simple read-only search with full schema documentation and complete annotation coverage, and no output schema (so return values need not be explained). Scope, optional filters, and pagination are all accounted for; nothing an agent needs in order to call it is missing.

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 every parameter is already documented with examples, defaults, and cross-references to sibling tools. The description merely restates query, storefront, category, and pagination at a higher level, adding no syntax or format meaning beyond the schema. Baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description gives a specific verb and resource ('Search products by query') plus the optional scoping dimensions, so an agent immediately knows what the tool does. It does not explicitly differentiate itself from siblings like get_product or search_services, though the 'search' framing versus lookup siblings is fairly intuitive.

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?

Usage is implied rather than stated: 'by query, optionally scoped' suggests this is the fuzzy-discovery tool versus a by-ID lookup, but it never names an alternative or a when-not-to-use condition. The schema mentions search_storefronts and get_categories, but that guidance lives in parameter descriptions rather than the tool description.

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

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