Skip to main content
Glama
Sign In

Paylo

by com.usepaylo
OverviewDiscussionsAdmin

search_storefronts

Read-onlyIdempotent

Discover verified, escrow-protected Paylo storefronts. Filter by Nigerian state, product category, area (LGA/city) and/or free text — e.g. 'phone sellers in Lagos' or 'beauty stores in Abuja'. Only quality-gated sellers are returned (verified, with a logo, a cover image and at least one live listing), ordered by number of live listings. Each result carries trust signals (verified, escrowProtected), location (state, area) and its storefront URL.

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_storefronts"
  }
}

Input Schema

NameRequiredDescriptionDefault
areaNoLGA/city area within a state, e.g. 'abuja-municipal'.
limitNoMax storefronts to return (1–200, default 50).
queryNoFree text over name, description, category and area.
stateNoNigerian state slug or name, e.g. 'lagos', 'ogun', 'abuja'/'FCT'.
categoryNoCanonical product category.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.1/5.0
Behavior5/5

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

Annotations already establish that this is a safe, read-only, idempotent, closed-world search. The description adds substantial behavior beyond that: only quality-gated sellers are returned, ordering is by number of live listings, and each result includes trust signals, location, and a storefront URL.

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?

The description is front-loaded with the core action and stays focused across a few tight sentences. Every sentence contributes either filtering guidance, quality-gating behavior, or return-content information.

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, but the description explains the key returned fields and ordering, which is enough for an agent to understand results. For a read-only search tool with fully documented parameters and rich annotations, no important calling context appears to be 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 coverage is 100%, so the input schema already documents all five parameters including examples and the category enum. The description reinforces that state, category, area, and free text can be combined, but it adds little parameter-level meaning beyond the schema.

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 clearly states a specific action and resource: discovering verified, escrow-protected Paylo storefronts. It does not explicitly contrast itself with sibling tools such as search_products or search_services, so sibling differentiation is implied by the storefront/seller focus rather than stated.

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?

It gives examples of filter combinations like 'phone sellers in Lagos' and 'beauty stores in Abuja', which implies when the tool is useful. However, it does not state when to use this instead of search_products, search_services, or get_storefront, nor does it list exclusions or prerequisites.

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