Skip to main content
Glama

list_utilities

Retrieve the full catalog of vetted utilities and agents from the CustomClaw registry. Returns JSON with utilities and agents arrays, results cached for 5 minutes.

Instructions

List every utility and agent available in the CustomClaw registry (https://customclaw.company). Results are cached for 5 minutes. Returns catalog JSON with utilities and agents arrays.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The handler for the 'list_utilities' tool: fetches the catalog (with 5-minute cache) and returns the full catalog JSON as the tool result.
    case 'list_utilities': {
      const catalog = await fetchCatalog();
      return jsonResult(catalog);
    }
  • index.js:189-200 (registration)
    The tool registration/definition, including name, description, and inputSchema (no parameters required) for 'list_utilities'.
    const TOOLS = [
      {
        name: 'list_utilities',
        description:
          'List every utility and agent available in the CustomClaw registry (https://customclaw.company). ' +
          'Results are cached for 5 minutes. Returns catalog JSON with utilities and agents arrays.',
        inputSchema: {
          type: 'object',
          properties: {},
          additionalProperties: false,
        },
      },
  • Input schema for 'list_utilities': empty object with no properties (no arguments required).
      inputSchema: {
        type: 'object',
        properties: {},
        additionalProperties: false,
      },
    },
  • The fetchCatalog helper function that retrieves catalog data with 5-minute TTL caching, used by the list_utilities handler.
    async function fetchCatalog({ force = false } = {}) {
      const now = Date.now();
      if (!force && catalogCache.data && now - catalogCache.ts < CATALOG_TTL_MS) {
        return catalogCache.data;
      }
      const res = await fetch(`${SITE_BASE}/api/catalog`);
      if (!res.ok) {
        throw new Error(`Catalog fetch failed: HTTP ${res.status}`);
      }
      const data = await res.json();
      catalogCache = { data, ts: now };
      return data;
    }
  • The jsonResult helper that formats the catalog data as a JSON text response.
    function jsonResult(obj) {
      return { content: [{ type: 'text', text: JSON.stringify(obj, null, 2) }] };
    }
Behavior4/5

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

With no annotations, the description discloses caching (5 minutes) and return structure (catalog JSON with utilities and agents arrays), which is transparent for a simple read-only tool. However, it does not mention authentication or error handling.

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 efficient sentences: first states purpose and source, second adds caching and return format. No wasted words.

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 tool with no parameters and no output schema, the description sufficiently covers the action, source, caching, and return format. It could mention the JSON structure details but is adequate.

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?

There are no parameters, so the baseline is 4. The description adds no parameter info since none exist.

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 uses a specific verb ('List') and resource ('every utility and agent') and distinguishes from siblings by indicating it returns all items from the registry, whereas siblings like get_utility_info or search_utilities likely target specific items.

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 broad listing use but does not explicitly state when not to use it or mention alternatives like search_utilities or get_utility_info for filtered queries.

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