Skip to main content
Glama

Search AI tools

search_ai_tools
Read-onlyIdempotent

Find AI tools for a task or need (e.g. "edit podcast audio", "AI video avatars", "SEO keyword research"), ranked by real web traffic. Optional filters: category, free plan only, max monthly price in USD. Returns tools with pricing, rank and a link to each tool's AIWiseRank page.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "query": "<query>"
    },
    "name": "search_ai_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat the user wants to do or the kind of tool, in plain words.
categoryNoOptional category: Software Engineering, Design & Creative, AI Models, Writing & Content, Customer Support, Productivity, Marketing & SEO, Data Analytics, Video Production, Sales Intelligence
free_plan_onlyNoOnly tools with a confirmed free plan or free tier.
max_monthly_usdNoBudget: only tools whose entry paid plan costs at most this much per month (USD list prices). Tools with a free plan always count as within budget.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedInput schema / properties / category / description
      Previous value: -"Optional category: Software Engineering, Design & Creative, AI Models, Customer Support, Writing & Content, Productivity, Marketing & SEO, Data Analytics, Video Production, Sales Intelligence"New value: +"Optional category: Software Engineering, Design & Creative, AI Models, Writing & Content, Customer Support, Productivity, Marketing & SEO, Data Analytics, Video Production, Sales Intelligence"
  2. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine context beyond that: results are ordered by real web traffic and include pricing, rank, and a page link, which tells the agent what to expect from the call. It does not mention result-count behavior or pagination truncation, keeping it below a 5.

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, front-loaded with the core purpose, then examples, then filters, then return shape. Every clause carries information and nothing is padded.

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?

With no output schema present, the description usefully compensates by summarizing the return payload (tools with pricing, rank, link). It is complete for selecting and calling the tool, with only the meaning/effect of 'limit' left implicit.

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 80%, and the schema already explains query phrasing, the category list, free_plan_only, and the budget rule including free-plan tools. The description only restates the filter set in summary form and adds no syntax or edge-case detail; the undocumented 'limit' parameter remains unexplained in both places, so this is baseline territory.

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?

The description states a specific verb and resource ('Find AI tools for a task or need'), plus the ranking basis (real web traffic) and what is returned (pricing, rank, AIWiseRank link). It is clearly a discovery-by-need search, implicitly distinct from get_ai_tool and compare_ai_tools, though no sibling is named explicitly.

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?

Concrete example queries ('edit podcast audio', 'AI video avatars') make the intended usage unambiguous, and the optional filters are framed as refinements. It stops short of stating when to prefer a sibling like best_ai_tools or compare_ai_tools instead, so no explicit exclusions or alternatives.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources