Skip to main content
Glama

gpu_catalog

Browse available AI compute services with pricing and model details to select GPU resources for AI applications.

Instructions

List all available GPU-Bridge services with pricing and model info. No authentication required.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The tool handler for "gpu_catalog" which fetches the catalog from the API and formats the output.
          case "gpu_catalog": {
            const catalog = await apiCall("/catalog", "GET");
            const services = catalog.services || [];
            const byCategory = {};
            for (const s of services) {
              const cat = s.category || "other";
              if (!byCategory[cat]) byCategory[cat] = [];
              const pricing = Object.values(s.pricing || {})[0] || `$${s.default_cost_usd}`;
              const models = (s.models || []).length;
              byCategory[cat].push(`  ${s.key} \u2014 ${s.name} (${pricing}${models ? `, ${models} models` : ""})`);
            }
            let text = `GPU-Bridge: ${catalog.active_endpoints} services available
    
    `;
            for (const [cat, items] of Object.entries(byCategory)) {
              text += `${cat.toUpperCase()}:
    ${items.join("\n")}
    
    `;
            }
            text += `Use gpu_run with service key and input to run any service.
    Use gpu_estimate to check cost before running.`;
            return { content: [{ type: "text", text }] };
          }
  • index.js:40-44 (registration)
    Registration of the "gpu_catalog" tool in the listTools response.
    {
      name: "gpu_catalog",
      description: "List all available GPU-Bridge services with pricing and model info. No authentication required.",
      inputSchema: { type: "object", properties: {} }
    },
Behavior3/5

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

No annotations provided, so description carries full disclosure burden. It successfully reveals authentication requirements and return data categories (pricing, model info). Missing operational details like rate limits, caching behavior, or pagination for large catalogs.

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 total with zero waste. Front-loaded with primary purpose ('List all available...'), followed by critical behavioral constraint ('No authentication required'). Every word earns its place.

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?

Appropriately complete for a simple catalog tool. Mentions return data content (pricing/model info) to compensate for missing output schema. Could be improved by indicating return format (array vs object) or pagination behavior.

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?

Zero parameters present, meeting the baseline score of 4 per rubric. Description appropriately focuses on behavioral semantics and return data rather than inventing parameter documentation where 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?

Clear specific verb 'List' with resource 'GPU-Bridge services' and scope details 'pricing and model info'. Effectively distinguishes from operational siblings (gpu_run, gpu_balance) by positioning as a catalog/browse function.

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?

States 'No authentication required' which provides a usage constraint, implying when it can be called safely. However, lacks explicit when-to-use guidance relative to siblings (e.g., 'use before gpu_run to select a model') or exclusion 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/gpu-bridge/mcp-server'

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