Skip to main content
Glama

Search AI tools for small businesses

search_tools
Read-only

Search the aitools.obzdn.co directory of AI and open-source tools for owner-operators and small teams. Returns up to limit tools, best match and highest-rated first, with what each does, who it fits, starting price, the catch to watch for, OBZDN's rating (top pick / also good / listed, and why), and links.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryYesWhat the business needs, in plain words, e.g. 'answer missed calls for a plumber'
audienceNoOptional audience id, e.g. trades (trades and home services), local (gyms, salons, studios, shops), pros (consultants, agencies, freelancers), creators, marketers
categoryNoOptional category id from https://aitools.obzdn.co/tools.json, e.g. missed-calls, estimates, scheduling, bookkeeping, reviews, content, email-marketing, local-seo
picks_onlyNoOptional: only OBZDN top picks (what we recommend for this need)
max_monthly_usdNoOptional: only tools whose starting price is at or under this many dollars
open_source_onlyNoOptional: only free and open-source tools

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed4 schema fields changed
    • changedInput schema / properties / audience / description
      Previous value: -"Optional: trades (trades and home services), local (gyms, salons, studios, shops), pros (consultants, agencies, freelancers), creators"New value: +"Optional audience id, e.g. trades (trades and home services), local (gyms, salons, studios, shops), pros (consultants, agencies, freelancers), creators, marketers"
    • removedInput schema / properties / audience / enum
      Removed value: -[
      -  "trades",
      -  "local",
      -  "pros",
      -  "creators"
      -]
    • changedInput schema / properties / category / description
      Previous value: -"Optional category id, e.g. missed-calls, estimates, scheduling, bookkeeping, reviews, field-photos, inbox, sales-followup, content, lead-gen, admin-docs"New value: +"Optional category id from https://aitools.obzdn.co/tools.json, e.g. missed-calls, estimates, scheduling, bookkeeping, reviews, content, email-marketing, local-seo"
    • addedInput schema / properties / picks_only
      Added value: +{
      +  "description": "Optional: only OBZDN top picks (what we recommend for this need)",
      +  "type": "boolean"
      +}
  2. First observed

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already mark this as a read-only, closed-world operation, and the description adds genuinely new behavioral facts: results are capped by `limit`, ordered by best match and highest rating, and each result carries rating rationale plus a 'catch to watch for'. It omits what happens on zero results, which is the main remaining gap.

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?

Two sentences, with the action and scope front-loaded and the return-field list trailing. The field enumeration is long but earns its place because there is no output schema to fall back on.

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, the description usefully enumerates what each result contains, so an agent knows it need not call get_tool for basic facts. Minor omissions: empty-result behavior and that limit maxes at 10.

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 86%, so the schema already documents all six optional filters with examples and enum-like values. The description adds only that `limit` bounds the result count and implies ranking affects ordering; it does not clarify how filters combine or whether category/audience ids are required to be valid.

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 (search) plus the exact resource (the aitools.obzdn.co directory of AI and open-source tools) and its target audience. It is immediately distinguishable from the sibling get_tool, which retrieves a single tool by identity rather than searching the catalog.

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?

The description implies discovery-then-detail flow (search returns summaries and links; get_tool presumably fetches the full record), but it never states when to use this versus get_tool or list_services, nor any exclusions. Usage is only inferable from the verb 'search'.

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