Skip to main content
Glama

search_catalog

Find AI agent services in the402.ai marketplace by keyword, category, type, or price range. Filter results by provider reputation and sort by relevance or price.

Instructions

Search the the402.ai service marketplace. Find AI agent services by keyword, category, service type, or price range. Returns service listings with pricing, descriptions, and provider reputation scores. No authentication required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryNoSearch keywords (full-text search with BM25 ranking)
categoryNoFilter by category
service_typeNoFilter by type: data_api (instant), automated_service (async), human_service (expert)
sortNoSort order (default: relevance)
min_reputationNoMinimum provider reputation score (0-100)
limitNoResults per page (default: 20, max: 100)
offsetNoPagination offset

Implementation Reference

  • The handler for the search_catalog tool which calls the client service endpoint.
    	async ({
    		query,
    		category,
    		service_type,
    		sort,
    		min_reputation,
    		limit,
    		offset,
    	}) => {
    		const params: Record<string, string> = {};
    		if (query) params.q = query;
    		if (category) params.category = category;
    		if (service_type) params.service_type = service_type;
    		if (sort) params.sort = sort;
    		if (min_reputation !== undefined)
    			params.min_reputation = String(min_reputation);
    		if (limit !== undefined) params.limit = String(limit);
    		if (offset !== undefined) params.offset = String(offset);
    
    		const result = await client.get("/v1/services/catalog", params);
    		return {
    			content: [
    				{ type: "text" as const, text: JSON.stringify(result, null, 2) },
    			],
    		};
    	}
    );
  • The Zod schema validation for search_catalog tool inputs.
    {
    	query: z
    		.string()
    		.optional()
    		.describe("Search keywords (full-text search with BM25 ranking)"),
    	category: z.string().optional().describe("Filter by category"),
    	service_type: z
    		.enum(["data_api", "automated_service", "human_service"])
    		.optional()
    		.describe(
    			"Filter by type: data_api (instant), automated_service (async), human_service (expert)"
    		),
    	sort: z
    		.enum(["relevance", "price_asc", "price_desc", "reputation"])
    		.optional()
    		.describe("Sort order (default: relevance)"),
    	min_reputation: z
    		.number()
    		.optional()
    		.describe("Minimum provider reputation score (0-100)"),
    	limit: z
    		.number()
    		.optional()
    		.describe("Results per page (default: 20, max: 100)"),
    	offset: z.number().optional().describe("Pagination offset"),
    },
  • The tool registration call for search_catalog.
    server.tool(
    	"search_catalog",
    	"Search the the402.ai service marketplace. Find AI agent services by keyword, category, service type, or price range. Returns service listings with pricing, descriptions, and provider reputation scores. No authentication required.",
Behavior4/5

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

With no annotations provided, the description carries full burden and does well by disclosing key behavioral traits: it describes the return format ('service listings with pricing, descriptions, and provider reputation scores') and explicitly states 'No authentication required.' However, it doesn't mention rate limits, pagination behavior beyond parameters, or error conditions.

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?

Three efficient sentences with zero waste: first states purpose, second details search dimensions, third covers returns and authentication. Every sentence earns its place and information is front-loaded appropriately.

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?

For a search tool with no annotations and no output schema, the description provides good coverage: purpose, usage context, return format, and authentication requirements. It could be more complete by mentioning pagination behavior or result format details, but covers the essentials well given the tool's complexity.

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 the schema already fully documents all 7 parameters. The description adds marginal value by mentioning the searchable dimensions (keyword, category, service type, price range) but doesn't provide additional semantic context beyond what's in the parameter descriptions.

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 description clearly states the specific action ('Search'), target resource ('the402.ai service marketplace'), and what it finds ('AI agent services'). It distinguishes this search tool from browsing or listing tools among siblings by focusing on keyword/category/price filtering.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides clear context for when to use this tool ('Find AI agent services by keyword, category, service type, or price range'), but doesn't explicitly state when NOT to use it or name specific alternatives among sibling tools like 'browse_products' or 'list_services' (if such existed).

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/the402ai/mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server