There's An AI For That

Search tools

search_tools

Read-only

Search the TAAFT directory for AI tools that match a query. Use url for TAAFT pages and website_url for external websites. Preserve returned URLs exactly.

Input Schema

TableJSON Schema

Name	Required	Description	Default
`sort`	No		default
`type`	No
`limit`	No
`query`	Yes	What the user needs an AI tool for.

Output Schema

TableJSON Schema

Name	Required	Description	Default
`tools`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedSep 7, 2026
- addedOutput schema / properties / tools / items / properties / website_url / description
```
Added value: +"TAAFT redirect to the external website. Preserve this URL exactly when sharing it."
```

Changed2 schema fields changedSep 7, 2026

addedOutput schema / properties / tools / items / properties / website_url
```
Added value: +{
+  "type": [
+    "string",
+    "null"
+  ]
+}
```

changedOutput schema / properties / tools / items / required

Previous value: -[
-  "name",
-  "slug",
-  "task",
-  "tagline",
-  "url"
-]New value: +[
+  "name",
+  "slug",
+  "task",
+  "tagline",
+  "url",
+  "website_url"
+]

First observedSep 6, 2026

TDQS

A4.1/5.0

Behavior4/5

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

Annotations cover read-only and non-destructive behavior, so the bar is lower. The description adds useful behavior beyond the schema: it distinguishes 'url' (for TAAFT pages) from 'website_url' (for external websites) and instructs the agent to preserve returned URLs exactly. This is meaningful operational guidance.

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 concise sentences with no filler. The first sentence states the core operation, and the second provides an important, actionable detail about URL fields. Information is front-loaded and efficient.

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 read-only search tool with an output schema and helpful annotations, the description covers the essential search context and URL handling. It does not describe result limits or sorting details, but nothing critical is missing for invoking the search correctly.

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

Parameters2/5

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

Schema description coverage is low (only 'query' is described), and the description does not explain 'sort', 'type', or 'limit' beyond what the enums already self-document. The URL guidance concerns response fields, not input parameters, so it does not compensate for the schema's low descriptive coverage.

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 uses a specific verb ('Search') and names the target resource ('TAAFT directory for AI tools that match a query'). This clearly distinguishes it from the sibling 'get_tool' by focusing on search-by-query rather than retrieval of a specific item.

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 makes the tool's context clear: use it to search the directory for AI tools based on a query. It does not explicitly say when not to use it or when to prefer get_tool, but the 'Search' framing plus the sibling name provide enough directional clarity without further exclusion instructions.

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

All There's An AI For That 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.