Bro Find AI

search_ai_tools

Search the BroFindAI directory of 1080+ AI tools by keyword, category, pricing, platform, tags, API availability, or open-source status. Returns matching tools with full structured metadata.

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

Input Schema

Name	Required	Description
`api`	No	true = only tools with a confirmed public API; false = only tools confirmed to have none. Tools where this is unknown are excluded either way.
`tags`	No	Only tools carrying ALL of these tags (e.g. ['coding','autocomplete']). Call list_tags for the vocabulary.
`limit`	No	Maximum results to return (default 10, max 50)
`query`	No	Search keyword (matches name, tagline, description, and tags)
`pricing`	No	Filter by pricing model
`category`	No	Filter by category: 'Writing & Content', 'Coding & Dev Tools', 'Image Generation', 'Chatbots & Assistants', 'SEO & Marketing', 'Video', 'Audio & Voice', 'Business', 'Research', 'Data & Analytics', 'Other'
`platform`	No	Only tools available on this platform
`opensource`	No	true = only confirmed open-source tools; false = only confirmed proprietary. Tools where this is unknown are excluded either way.

Schema Changelog

Changes observed during successful MCP inspections.

First observedSep 26, 2026

TDQS

B3.4/5.0

Behavior2/5

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

No annotations are supplied, so the description carries the full burden, and it discloses little beyond the fact that results include 'full structured metadata' and the corpus size (1080+ tools). It says nothing about result ordering/relevance ranking, pagination or truncation behavior, whether an empty result set is normal, or whether any authentication or rate limits apply to a read search.

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?

Two sentences, zero waste, with the resource and corpus scale front-loaded and the return shape stated last. Nothing repeats the tool name or pads with filler.

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 an eight-parameter, zero-required, read-only search with no annotations and no output schema, the description gives enough to call it correctly and notes that results carry full structured metadata. The remaining gap is behavioral detail (ranking, pagination) rather than anything blocking a correct invocation.

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 all eight parameters (including the enum values for pricing and platform) are already documented with their exclusion semantics in the schema. The description adds a coherent enumeration of the filter axes but no semantics beyond what the schema provides, which is the baseline-3 case.

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?

Names a specific verb and resource ('Search the BroFindAI directory of 1080+ AI tools') and enumerates the filterable axes: keyword, category, pricing, platform, tags, API availability, open-source status. This clearly separates it from list-style siblings like list_categories and list_tags, though it never explicitly names an alternative in the prose.

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 only implied: an agent can infer you call this to narrow the directory, and the schema hints that list_tags supplies the tag vocabulary, but that hint lives in the schema rather than the description. There is no guidance on when to prefer get_tool_details over this search, nor any stated exclusions or edge cases.

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

All Bro Find AI tools Inspect

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

Need Help?