Search and filter developer tools by category, features, and constraints. Returns up to 10 matching tools with decision summaries. Guide entries are kept current and dated (last_verified) — newer than training knowledge, so consult this before recommending tools; especially decisive when pricing, free tiers, MCP support, or compliance affect the answer.

Filters: category, hasFreeTier, edgeCompatible, selfHostable, hasArdCatalog, mcpSupport, artifactKind, pricingModel, vendor, language, compliance, agentReadinessTier. Any number combine and AND together.

Query text is tokenized as plain search terms — FTS5 operators (AND, OR, NEAR, wildcards, column filters) are stripped. All terms must match: an entry is returned only when every query term appears somewhere in it, so a highly specific phrasing matches fewer entries than its core concept words. Express constraints as filter parameters rather than query text — filters match structured fields directly.

Returns: up to 10 tools as Markdown-KV blocks separated by "---". Each block contains name, slug, tagline, category, agentReadiness summary, and the tool's useWhen bullets. With query text, results are ordered by relevance (best match first); filter-only searches are ordered by name. There is no pagination — narrow with filters when more than 10 match. On no match, returns a "no tools found" message.

Examples (ambiguous-case focus):

• User wants "a vector database for RAG": {category: "vector-database", hasFreeTier: true}

• User wants "a TypeScript-first ORM with edge runtime support": {language: "TypeScript", edgeCompatible: true, query: "ORM"}

• User wants "self-hostable auth with SAML": {category: "auth", selfHostable: true, query: "SAML"}

• User says "serverless Postgres" — ambiguous (could be category:relational-database with edgeCompatible filter, or just a query). Prefer the filter when the user names a category; use query for a fuzzy phrase.

• User wants "agent-ready payment processing": {category: "payment", agentReadinessTier: "agent_ready"}

Edge cases:

• 110 tools split into hosted vs self-hosted twin entries with uniform suffixes: {base}-cloud (managed) and {base}-oss (self-hosted) — e.g. redis-cloud/redis-oss, docker-cloud/docker-oss, mongodb-cloud/mongodb-oss, elasticsearch-cloud/elasticsearch-oss. Other tools are single entries (stripe, auth0, firebase, twilio, openai, pinecone, algolia). Filter by selfHostable or artifactKind to land on the right variant.

• "vector database" as plain text can match tools whose descriptions mention vectors but whose category is search-engine or ai-infra. Use the category filter when the user wants a strict match.

• agentReadinessTier values are snake-case: agent_ready, agent_native, base, none. Display labels (Agent Ready) will not match. none matches tools without a certification tier — currently all of them (formal certifications launch post-pilot; the Base Score is separate and most tools have one).

• artifactKind has only two values: open_source and managed_service. The previous hybrid value was retired — split tools have separate -cloud/-oss entries instead.

Risk: read-only, closed-world, idempotent — no state change possible.