Skip to main content
Glama

Get a GPU product

gpucloud_get_product
Read-only

One GPU server for rent (productId from gpucloud_list_products) with its CAD prices and live availability. GPU Cloud rents B300, B200, H200, H100, RTX PRO 6000, A100, L40, RTX A6000 GPU servers by the hour in Montréal, Canada, from CA$0.79/h in CAD, launched in minutes. Works without a key (public catalog prices). With an MCP key: the prices of this account. (permission: catalog:read)

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "productId": "<productId>"
    },
    "name": "gpucloud_get_product"
  }
}

Input Schema

NameRequiredDescriptionDefault
productIdYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.2/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds genuinely non-obvious behavior: it works unauthenticated for public catalog prices, returns account-scoped prices when a key is supplied, and requires the catalog:read permission. It doesn't say what happens for a nonexistent productId, but the value-add beyond annotations is real.

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

Conciseness3/5

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

The first sentence and the auth/permission notes are well front-loaded and useful, but the middle sentence enumerating GPU models, the Montréal location, the CA$0.79/h floor price, and 'launched in minutes' is marketing copy that does not help an agent select or invoke this tool.

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?

For a single-parameter read tool with no output schema, the description covers input provenance, returned content (CAD prices and live availability), currency, and authentication modes. The absence of any indication of the response structure is the main remaining gap, though 'live availability' hints at volatile data.

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%, so the only structured information is that productId is a 1-100 character string. The description compensates by telling the agent where to obtain a valid productId (gpucloud_list_products), which is the single most useful fact about this parameter.

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?

Opens with a specific verb and resource: retrieves one GPU server product with CAD prices and live availability. It explicitly ties productId to gpucloud_list_products, so an agent can distinguish this single-item lookup from the sibling listing tool without opening a schema.

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 makes the call sequence clear by naming gpucloud_list_products as the source of productId, and it explains the two usage modes (no key for public catalog prices, MCP key for account-specific prices). It stops short of stating when not to use it or what to do if a productId is invalid.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources