Skip to main content
Glama

WhatAreYouBuilding.AI

by ai.whatareyoubuilding
OverviewDiscussionsAdmin

Search products

search_products
Read-onlyIdempotent

Search the directory of builder products. Filter by free text, region, category, funding stage, whether the builder is actively raising, and what they are open to. Returns the matching products with their builder attribution and engagement stats. Call this whenever someone wants to find products or the people behind them by any of those axes — "who is building fintech in Nigeria", "indie AI tools whose founders are raising", "what has this person shipped". It is the right tool for deal sourcing and scouting: raising_status and open_to together answer "who wants to hear from an investor", and region is the axis this directory is organised around. Do not call it to rank or compare products by traction — that is get_leaderboard. Do not call it when you already hold a product id; get_product returns more per record. Funding is opt-in: funding_stage may be "undisclosed" and actively_raising may be null, both meaning the builder declined to say rather than that the answer is no.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
sortNoResult ordering. Defaults to recent.
limitNoMax results, 1-100. Defaults to 25.
queryNoFree text matched against product name, one-liner, builder name, category, region and city. Every word must match.
offsetNoResults to skip, for paging.
regionNoCountry name, e.g. "Israel", "United States", "Nigeria". Case-insensitive. Omit for all regions.
open_toNoReturn only products open to this kind of contact.
categoryNoProduct category, e.g. "AI", "Fintech", "Dev Tools". Call list_filters for the full list. A listing may carry up to three, and this matches any of them.
funding_stageNoFunding stage of the product. "undisclosed" means the builder chose not to state a stage; it is not a stage between or below the others, and it does not imply bootstrapped.
raising_statusNoWhether the builder is raising, as three distinct answers. "raising" = they said yes. "not_raising" = they said no. "undisclosed" = they declined to say, which is NOT the same as no and must never be reported as no. Independent of funding_stage. Prefer this over actively_raising.
actively_raisingNoTwo-value shorthand for raising_status: true is "raising", false is "not_raising". Neither value returns builders who declined to disclose; ask for raising_status="undisclosed" to see those. raising_status wins if both are sent.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.6/5.0
Behavior4/5

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

Annotations already declare the safe read-only/idempotent profile, so the bar is lower. The description still adds real behavioral context: the opt-in funding caveat that 'undisclosed' and null mean the builder declined to say rather than 'no', and that results carry builder attribution and engagement stats.

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?

Reasonably long but well-structured and front-loaded: purpose, then filter axes, then return, then usage rules. The examples and exclusion sentences earn their place; only slight tightening would reach 5.

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?

For a 10-parameter, zero-required search tool with no output schema, the description covers filtering axes, return contents (products with builder attribution and engagement stats), and the subtle tri-state funding semantics. Nothing needed to invoke it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it frames region as the directory's organizing axis and explains that raising_status and open_to together answer 'who wants to hear from an investor', and reinforces the undisclosed semantics.

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?

States a specific verb and resource ('Search the directory of builder products') and enumerates the filtering axes. It explicitly distinguishes itself from siblings get_leaderboard and get_product, so an agent can route correctly without opening schemas.

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

Usage Guidelines5/5

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

Gives explicit when-to-use with concrete user-phrasing examples, plus when-NOT-to-use with named alternatives ('Do not call it to rank or compare products by traction — that is get_leaderboard', 'when you already hold a product id; get_product'). Nothing is left to inference.

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

All WhatAreYouBuilding.AI 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