Skip to main content
Glama

colab_pool_status

Read-only

Check shared Colab VM availability, open slots, queued jobs, and compute-unit balance before submitting or scheduling work.

Instructions

List shared Colab VMs, available slots, queued jobs, and the compute-unit balance.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "colab_pool_status"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds real value by enumerating what the response surfaces, but says nothing about scope (all pools vs. the caller's), freshness of the slot/job counts, or result size — all relevant for an open-world read.

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?

One sentence, verb front-loaded, and every listed item is distinct information an agent would act on. Nothing is repeated from the annotations or padded.

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?

With no input parameters and no output schema, the description carries the burden of describing the return payload, and it does so by naming all four returned categories. The remaining gap is scope and freshness — whether the listing is global and whether the counts are live.

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?

The tool takes zero parameters and the schema coverage is complete, so there is no parameter meaning to convey; the description correctly spends no words on inputs. Baseline 4 applies for a no-parameter tool.

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?

"List" plus four concrete resources (shared VMs, available slots, queued jobs, compute-unit balance) tells an agent exactly what comes back, and the pooled-resource framing separates it from the per-job sibling colab_job_status. It stops short of explicitly naming that sibling, so the differentiation is inferential rather than stated.

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?

The description never says when to call this versus colab_job_status or colab_pool_stop, nor any prerequisite such as checking capacity before colab_run_job. Usage is only inferable from the enumerated outputs, which matches the 'no when-to-use guidance' level.

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