Skip to main content
Glama

Search AI tools

search_tools
Read-onlyIdempotent

Use this when the user wants to find AI tools for a task, optionally within a budget, skill level or platform. Returns Launchpad HQ catalog matches with dated, sourced free-tier facts where available. Items with fallback: true are popular tools, not direct matches; stale: true means the facts are over 90 days old.

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": {
      "task": "<task>"
    },
    "name": "search_tools"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskYesWhat the user wants to do, e.g. 'transcribe meetings' or 'make slides'. Only the first 200 characters are searched.
limitNoMax results (1-10, default 5).
budgetNoBudget band. 'free' keeps only free or freemium tools; 'low' keeps free/freemium tools or a lowest paid plan up to $20/month, 'medium' up to $50/month (unknown prices rank lower).
skill_levelNoUser's skill level. Tools above it rank lower.
platform_typeNoTools available there rank first.

Output Schema

NameRequiredDescriptionDefault
noteYes
queryYes
resultsYes
fallbackNo
data_as_ofYes
attributionYes
total_matchesYes
corrected_queryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed11 schema fields changed
    • changedInput schema / properties / budget / description
      Previous value: -"Budget band. 'free' keeps only free or freemium tools."New value: +"Budget band. 'free' keeps only free or freemium tools; 'low' keeps free/freemium tools or a lowest paid plan up to $20/month, 'medium' up to $50/month (unknown prices rank lower)."
    • addedInput schema / properties / platform_type / description
      Added value: +"Tools available there rank first."
    • changedInput schema / properties / task / description
      Previous value: -"What the user wants to do, e.g. 'transcribe meetings' or 'make slides'."New value: +"What the user wants to do, e.g. 'transcribe meetings' or 'make slides'. Only the first 200 characters are searched."
    • changedInput schema / properties / task / maxLength
      Previous value: -200New value: +1000
    • addedOutput schema / properties / corrected_query
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / fallback
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "starter",
      +        "top_up"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / fallback
      Added value: +{
      +  "type": "boolean"
      +}
    • addedOutput schema / properties / results / items / properties / freshness_note
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / resolution
      Added value: +{
      +  "anyOf": [
      +    {
      +      "enum": [
      +        "compact",
      +        "alias",
      +        "spelling"
      +      ],
      +      "type": "string"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / resolved_from
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / results / items / properties / stale
      Added value: +{
      +  "type": "boolean"
      +}
  2. Changed1 schema field changed
    • addedOutput schema / properties / results / items / properties / tasks
      Added value: +{
      +  "anyOf": [
      +    {
      +      "items": {
      +        "type": "string"
      +      },
      +      "type": "array"
      +    },
      +    {
      +      "type": "null"
      +    }
      +  ]
      +}
  3. First observed

TDQS

A4.1/5.0
Behavior4/5

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

Adds real context beyond the annotations: results are dated and sourced, fallback: true marks popular-but-non-matching tools, stale: true marks facts over 90 days old. These are important interpretation cues. It does not mention result-count behavior or coverage limits of the catalog.

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?

Three short sentences, front-loaded with the usage condition and followed by the return payload and flag semantics. No filler.

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?

An output schema exists so return shape need not be explained, yet the description still clarifies the two ambiguous response flags. Nothing an agent needs in order to call this correctly is missing.

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 coverage is 100% and enums are fully documented, so the baseline applies. The description only restates the optional filters at a high level ('optionally within a budget, skill level or platform') without adding semantics such as how budget interacts with pricing data.

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?

States a specific verb and resource ('find AI tools') with scope ('returns Launchpad HQ catalog matches'). It does not name or contrast with siblings, notable given find_free_alternatives overlaps with the budget=free case.

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?

'Use this when the user wants to find AI tools for a task, optionally within a budget, skill level or platform' gives a clear triggering condition. It stops short of stating when NOT to use it (e.g. pricing-only questions that belong to get_pricing_facts).

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.