Skip to main content
Glama

get_utility_info

Retrieve the full catalog entry for a utility or agent by slug, including name, tagline, description, price, free flag, and category.

Instructions

Return the full catalog entry for a single utility or agent by slug (name, tagline, description, price, free flag, category, etc.).

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
slugYesThe utility or agent slug, e.g. "token-optimiser".

Implementation Reference

  • The handler logic for the 'get_utility_info' tool. It validates the 'slug' argument, fetches the catalog, looks up the entry by slug via findBySlug(), and returns the entry as JSON or an error message.
    case 'get_utility_info': {
      if (!args.slug || typeof args.slug !== 'string') {
        return textResult('Error: slug is required (string).');
      }
      const catalog = await fetchCatalog();
      const entry = findBySlug(catalog, args.slug);
      if (!entry) {
        return textResult(
          `No utility or agent with slug "${args.slug}". Use search_utilities or list_utilities to find valid slugs.`
        );
      }
      return jsonResult(entry);
    }
  • The schema/definition of the 'get_utility_info' tool, including its name, description, and inputSchema (requiring a 'slug' string property).
    {
      name: 'get_utility_info',
      description:
        'Return the full catalog entry for a single utility or agent by slug (name, tagline, description, price, free flag, category, etc.).',
      inputSchema: {
        type: 'object',
        properties: {
          slug: {
            type: 'string',
            description: 'The utility or agent slug, e.g. "token-optimiser".',
          },
        },
        required: ['slug'],
        additionalProperties: false,
      },
    },
  • index.js:189-263 (registration)
    The TOOLS array where 'get_utility_info' is registered alongside the other three tools. The array is returned by the ListToolsRequestSchema handler.
    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,
        },
      },
      {
        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,
        },
      },
      {
        name: 'get_utility_info',
        description:
          'Return the full catalog entry for a single utility or agent by slug (name, tagline, description, price, free flag, category, etc.).',
        inputSchema: {
          type: 'object',
          properties: {
            slug: {
              type: 'string',
              description: 'The utility or agent slug, e.g. "token-optimiser".',
            },
          },
          required: ['slug'],
          additionalProperties: false,
        },
      },
      {
        name: 'install_utility',
        description:
          'Fetch a CustomClaw utility payload and write its files into target_dir. ' +
          'For paid utilities, pass session_id (the Stripe checkout session_id from the buyer\'s receipt email). ' +
          'Returns the list of files written and any npm dependencies the caller should install — ' +
          'this tool does NOT run npm install itself; the host agent decides when to install deps.',
        inputSchema: {
          type: 'object',
          properties: {
            slug: {
              type: 'string',
              description: 'The utility slug to install.',
            },
            target_dir: {
              type: 'string',
              description:
                'Directory to write files into. Absolute path preferred; relative paths are resolved against the server process cwd.',
            },
            session_id: {
              type: 'string',
              description:
                'Optional. Stripe checkout session_id for paid utilities. Found as session_id=... in the CustomClaw receipt email download URL.',
            },
          },
          required: ['slug', 'target_dir'],
          additionalProperties: false,
        },
      },
    ];
  • The findBySlug() helper function used by the handler to locate a utility/agent entry by slug from the catalog.
    function findBySlug(catalog, slug) {
      return allEntries(catalog).find((e) => e.slug === slug) || null;
    }
Behavior3/5

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

No annotations are present, so the description must cover behavior. It indicates a read operation without side effects, but does not address error cases (e.g., missing slug), authentication needs, or rate limits. This is adequate for a simple retrieval but lacks full transparency.

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 a single sentence that efficiently conveys the core function and included fields, with no extraneous information. It is well-structured and front-loaded.

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 single-parameter schema and no output schema, the description adequately explains what the tool returns and how to use it. It could mention the outcome for invalid slugs, but overall it is sufficiently complete for its complexity.

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?

The input schema covers 100% with a description for 'slug'. The description's mention of 'by slug' mirrors the schema, adding no new semantic value beyond what the schema already provides. Therefore, the baseline score of 3 applies.

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 clearly states the tool returns a full catalog entry for a single utility/agent by slug, listing specific fields (name, tagline, description, price, etc.). It differentiates from sibling tools like list_utilities and search_utilities, which handle multiple results.

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?

The description specifies the required identifier (slug) but does not explicitly provide when or when not to use this tool versus siblings. However, the context of siblings implies that get_utility_info is for a single detailed entry, while list_utilities gives an overview and search_utilities finds by criteria.

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