Skip to main content
Glama

gpu_status

Check GPU-Bridge job status and retrieve results using the job ID from gpu_run. Monitor AI compute tasks across multiple backends.

Instructions

Check the status of a GPU-Bridge job and retrieve results.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
job_idYesThe job ID returned by gpu_run

Implementation Reference

  • The handler for the 'gpu_status' tool, which fetches job status from the API and returns the result or current progress to the user.
          case "gpu_status": {
            const { job_id } = args;
            const status = await apiCall(`/status/${job_id}`, "GET");
            let text = `Job ${status.id}: ${status.status}`;
            if (status.progress) {
              text += `
    Progress: ${status.progress.phase} (${status.progress.percent_estimate}%, ${status.progress.elapsed_seconds}s elapsed)`;
            }
            if (status.output) {
              const o = status.output;
              if (o.text) text += `
    Output: ${o.text}`;
              else if (o.url) text += `
    Output: ${o.url}`;
              else if (o.audio_url) text += `
    Output: ${o.audio_url}`;
              else text += `
    Output: ${JSON.stringify(o)}`;
            }
            if (status.error) {
              text += `
    Error: ${status.error}`;
              if (status.refunded) text += ` (refunded $${status.refund_amount_usd})`;
            }
            if (status.output_notice) text += `
    Note: ${status.output_notice}`;
            return { content: [{ type: "text", text }] };
          }
  • Registration of the 'gpu_status' tool, including its description and input schema (requiring 'job_id').
      name: "gpu_status",
      description: "Check the status of a GPU-Bridge job and retrieve results.",
      inputSchema: {
        type: "object",
        properties: {
          job_id: { type: "string", description: "The job ID returned by gpu_run" }
        },
        required: ["job_id"]
      }
    },
Behavior3/5

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

With no annotations provided, the description carries the full burden. It mentions 'retrieve results' indicating output behavior, but omits critical async details: whether this blocks, if repeated polling is expected, result expiration, or what status values (e.g., running, completed, failed) are possible.

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?

Single efficient sentence with no filler. Information is front-loaded (action + subject + outcome). Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Adequate for a single-parameter tool, but lacking given the absence of an output schema. For a status retrieval tool, describing the possible status states or result payload structure would significantly improve completeness.

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 coverage is 100% with job_id well-documented. The description mentions 'GPU-Bridge job' which loosely contextualizes the parameter, but adds no syntax details, format constraints, or examples beyond what the schema already provides. Baseline 3 is appropriate given high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clear verb ('Check') and resource ('GPU-Bridge job'), plus outcome ('retrieve results'). However, it does not explicitly differentiate from siblings like gpu_run or gpu_catalog within the description text, relying instead on the tool name to signal its polling/retrieval role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides no explicit guidance on when to use this tool versus alternatives, or that it requires a job_id from gpu_run first. The schema parameter description mentions it returns job IDs from gpu_run, but the main description lacks usage context.

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