Skip to main content
Glama

search_utilities

Search the CustomClaw registry of vetted utilities using fuzzy keyword matching across names, descriptions, and categories. Returns top 25 relevant results.

Instructions

Fuzzy-search the CustomClaw registry by keyword. Matches across slug, name, tagline, description, and category. Returns the top 25 matches sorted by relevance.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
queryYesKeyword(s) to search for, e.g. "token optimiser" or "stripe".

Implementation Reference

  • index.js:201-217 (registration)
    Tool registration for 'search_utilities' defining name, description, and inputSchema.
    {
      name: 'search_utilities',
      description:
        'Fuzzy-search the CustomClaw registry by keyword. Matches across slug, name, tagline, description, and category. ' +
        'Returns the top 25 matches sorted by relevance.',
      inputSchema: {
        type: 'object',
        properties: {
          query: {
            type: 'string',
            description: 'Keyword(s) to search for, e.g. "token optimiser" or "stripe".',
          },
        },
        required: ['query'],
        additionalProperties: false,
      },
    },
  • Handler case in CallToolRequestSchema that executes search_utilities logic: validates query, fetches catalog, calls fuzzySearch, and returns matches.
    case 'search_utilities': {
      if (!args.query || typeof args.query !== 'string') {
        return textResult('Error: query is required (string).');
      }
      const catalog = await fetchCatalog();
      const matches = fuzzySearch(catalog, args.query);
      if (matches.length === 0) {
        return textResult(`No matches for "${args.query}". Try list_utilities to browse the full catalog.`);
      }
      return jsonResult({ query: args.query, count: matches.length, results: matches });
    }
  • fuzzySearch helper: scores all entries against the query, filters by score > 0, sorts descending by score, returns top 25 matches.
    function fuzzySearch(catalog, query) {
      return allEntries(catalog)
        .map((e) => ({ entry: e, score: scoreMatch(e, query) }))
        .filter((x) => x.score > 0)
        .sort((a, b) => b.score - a.score)
        .slice(0, 25)
        .map((x) => x.entry);
    }
  • scoreMatch helper: scores an entry against a query string by comparing slug, name, tagline, description, and category fields with weighted fuzzy matching (exact match, includes, token match).
    function scoreMatch(entry, q) {
      const query = q.toLowerCase().trim();
      if (!query) return 0;
      const fields = [
        [entry.slug || '', 4],
        [entry.name || '', 3],
        [entry.tagline || '', 2],
        [entry.description || '', 1],
        [entry.category || '', 1],
      ];
      let score = 0;
      for (const [val, weight] of fields) {
        const v = String(val).toLowerCase();
        if (!v) continue;
        if (v === query) score += weight * 10;
        else if (v.includes(query)) score += weight * 3;
        else {
          // token match
          const tokens = query.split(/\s+/).filter(Boolean);
          for (const t of tokens) {
            if (v.includes(t)) score += weight;
          }
        }
      }
      return score;
    }
Behavior4/5

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

With no annotations, the description carries full burden. It discloses fuzzy matching behavior, fields searched, result limit of 25, and relevance-based sorting. While it does not mention pagination or error handling, the provided traits are sufficient for a read-only search operation.

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?

The description is two sentences, front-loaded with purpose, and every sentence adds value. No extraneous information, efficiently conveying scope and behavior.

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?

Given the simple tool with one parameter and no output schema, the description adequately covers input (keyword) and output (top 25 sorted results). It lacks mention of empty results or pagination but is complete for typical use.

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

Parameters4/5

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

Schema coverage is 100% with a single query parameter already described with examples. The description adds meaningful context beyond schema by specifying fuzzy matching and the fields searched, enhancing understanding of how the parameter is used.

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 states 'Fuzzy-search the CustomClaw registry by keyword' with specific verb and resource. It details matching fields (slug, name, tagline, description, category) and output (top 25 sorted by relevance), clearly distinguishing it from siblings like get_utility_info (specific utility) or list_utilities (all utilities).

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 usage for keyword search but does not explicitly state when to use this tool versus alternatives (e.g., for exact match use list_utilities, for specific utility use get_utility_info). No exclusion criteria or when-not-to-use guidance is provided.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/onlythebestswfl-ops/customclaw-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server