Skip to main content
Glama
Sign In

PayAPI Market

by market.payapi
OverviewDiscussionsAdmin

Search AI agents on PayAPI Market

search_agents
Read-onlyIdempotent

Search AI agents by business sector, name, or description. Agents are AI services that perform tasks like lead generation, data enrichment, or automation. Returns agents with their sector, pricing, and verified status. Free and read-only.

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

Input Schema

NameRequiredDescriptionDefault
sortNoSort order: newest (default), rating (top-rated), or verified_calls (most used).newest
limitNo
queryNoSearch query: name, description, or sector (e.g. "real estate" or "lead generation").
sectorNoFilter by business sector: home_services, real_estate, ecommerce, marketing, sales, finance, legal, healthcare, recruiting, support, developer_tools, crypto, or other.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Added

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the description's 'read-only' adds little, though 'Free' contributes new cost information. It also discloses the shape of returned records (sector, pricing, verified status), which matters since there is no output schema, but says nothing about result caps, pagination, or how limit interacts with total matches.

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?

Four short sentences with the purpose front-loaded, followed by domain clarification, return fields, and safety/cost. Nothing is redundant except the mild overlap between 'read-only' and the readOnlyHint annotation.

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

Completeness4/5

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

With zero required parameters, no output schema, and a simple flat schema, the description covers what the tool searches, what it returns, and that it is free and safe. The main residual gap is pagination/result-cap behavior, which matters for a search tool with a limit parameter.

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 75% and the sort, query, and sector fields are well documented, so the baseline is 3. The description reinforces that query spans name, description, or sector, but adds no syntax or behavior beyond what the schema already states, and the undescribed 'limit' parameter gets no compensating explanation.

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?

States a specific verb and resource ('Search AI agents') plus the three searchable dimensions (sector, name, description), and clarifies what an 'agent' is so the term isn't ambiguous. It does not explicitly distinguish itself from search_apis or list_apis, leaving that differentiation to the tool name alone.

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 closing 'Free and read-only' implies this is safe to call freely, and the sector/query framing hints at when it applies. However, there is no explicit guidance on when to choose this over search_apis, get_api, or list_apis, nor any note on how to combine query with sector.

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

All PayAPI Market 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