Skip to main content
Glama

setup_guide

Guides connecting Google Colab, Kaggle, Hugging Face, or Spaces for GPU runs; with no platform specified, reports which connections are configured and what remains missing.

Instructions

How to connect a place to run on: "colab", "kaggle", "huggingface" or "space".

With no platform it reports what is already set up and what is missing. Use this whenever the user asks how to connect, or a tool says nothing is connected.

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": "setup_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
platformNo

Output Schema

NameRequiredDescriptionDefault
resultYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.4.0

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the full burden. It does disclose the important no-argument behavior (reports current setup state and gaps), which is genuine behavioral context, but it never clarifies whether calling it merely returns instructions or actually performs a connection — a critical ambiguity given siblings like connect_runtime and colab_runtime_start.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs, front-loaded with the main behavior and followed by the no-platform case and usage trigger. Minor awkwardness in phrasing ("a place to run on") but no wasted sentences.

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?

An output schema exists, so return values need not be explained. However, for a tool sitting beside many runtime-connection siblings, the description omits the one fact an agent most needs: whether this guides the user or executes the connection, leaving the choice between this and connect_runtime-style tools underspecified.

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?

Schema coverage is 0% and the platform parameter is a bare optional string, so the description does the work by enumerating the accepted values (colab, kaggle, huggingface, space) and explaining the empty/default case. It would be stronger if it warned about invalid values or case sensitivity.

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?

The description names the resource (a place to run on) and enumerates the four supported platforms, plus states the no-argument behavior of reporting what is set up versus missing. It is clear enough to distinguish a guidance/inspection tool from action tools, though the verb is implicit ("how to connect") rather than stated as an operation.

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?

Gives two explicit trigger conditions: when the user asks how to connect, and when another tool reports nothing is connected. It offers no exclusions or named alternatives, so the agent must infer when to prefer the action-oriented siblings over this guide.

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