Skip to main content
Glama

Search AI tools

search_tools
Read-only

Search the hand-checked list of AI tools by words, by category, or both. Sponsored tools (at most 3 per category, taking turns each day) come at the top of a category and are marked.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNoWords to match, e.g. "video editor"
categoryNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already establish that this is a safe, closed-world read operation, so the description's safety burden is low. It does add genuinely useful result-ordering context: sponsored tools appear at the top of a category, capped at three, rotate daily, and are marked. That is valuable, but it leaves other behavioral details such as pagination or matching semantics unstated.

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 what the tool does and the search modes, followed by non-obvious ranking behavior. Every sentence earns its place and nothing is redundant.

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 no output schema, the definition covers the essential search modes and the unusual sponsored-placement behavior. It is nearly complete; the main remaining gaps are guidance against sibling tools and the semantics of the limit parameter, but neither is severe for a simple search endpoint.

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 33%: query has an example and category has a rich enum, but limit has no descriptive text. The description partially compensates by clarifying that query and category are independently optional and can be combined ('by words, by category, or both'), but it says nothing about the limit parameter or its default behavior.

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 gives a specific verb (Search) and resource (hand-checked list of AI tools) and names the searchable dimensions: words, category, or both. It is clear what the tool does, but it does not differentiate itself from siblings like get_tool or list_categories, which an agent might otherwise consider for related lookup tasks.

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 implied by the phrase 'by words, by category, or both,' which tells the agent these modes can be combined. However, there is no explicit when-to-use guidance or exclusion relative to alternatives such as get_tool for a known tool name or list_categories for browsing categories.

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