Skip to main content
Glama

get_rental_quote

Read-only

Direct rentals from Galaxy Mind have closed. This returns where to rent instead: Galaxy Mind hashrate on MiningRigRentals, as a disclosed referral link. It gives no price and places no order.

Input Schema

NameRequiredDescriptionDefault
phNoAlternatively, the hashrate wanted in PH/s, up to 1.08. 270 TH minimum; rounded to whole rigs. Overrides rigs.
daysNoRental length in whole days, 1 to 7 during the pilot. Defaults to 1.
rigsNoNumber of whole S21 XP rigs (270 TH each), 1 to 4 per order. Defaults to 1.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changed
    • changedInput schema / properties / days / description
      Previous value: -"Rental length in whole days, 1 to 7 days during the pilot, up to 30 later. Defaults to 1."New value: +"Rental length in whole days, 1 to 7 during the pilot. Defaults to 1."
    • changedInput schema / properties / rigs / description
      Previous value: -"Number of whole S21 XP rigs (270 TH each, 270 TH minimum), 1 to 4. Defaults to 1."New value: +"Number of whole S21 XP rigs (270 TH each), 1 to 4 per order. Defaults to 1."
  2. Changed1 schema field changed
    • changedInput schema / properties / days / description
      Previous value: -"Rental length in whole days, 1 to 30. Defaults to 1."New value: +"Rental length in whole days, 1 to 7 days during the pilot, up to 30 later. Defaults to 1."
  3. Changed5 schema fields changed
    • addedInput schema / properties / days
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Rental length in whole days, 1 to 30. Defaults to 1."
      +}
    • removedInput schema / properties / hours
      Removed value: -{
      -  "description": "Rental window in hours. Defaults to 3. Values outside a machine's real window clamp to it, with a note.",
      -  "exclusiveMinimum": 0,
      -  "maximum": 168,
      -  "type": "number"
      -}
    • removedInput schema / properties / machineId
      Removed value: -{
      -  "description": "One of Galaxy Mind's MiningRigRentals rig ids. Omit to quote every machine at once.",
      -  "type": "string"
      -}
    • addedInput schema / properties / ph
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Alternatively, the hashrate wanted in PH/s, up to 1.08. 270 TH minimum; rounded to whole rigs. Overrides rigs."
      +}
    • addedInput schema / properties / rigs
      Added value: +{
      +  "anyOf": [
      +    {
      +      "type": "number"
      +    },
      +    {
      +      "type": "string"
      +    }
      +  ],
      +  "description": "Number of whole S21 XP rigs (270 TH each, 270 TH minimum), 1 to 4. Defaults to 1."
      +}
  4. Added

TDQS

A3.9/5.0
Behavior4/5

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

Annotations already cover readOnly and openWorld safety profile. The description adds valuable context beyond them: that direct rentals are closed, that the result is a disclosed referral link, and explicitly that it returns no price and places no order — preventing an agent from misusing it as a pricing or booking call. No contradictions.

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?

Three short, front-loaded sentences with no wasted words. The status context leads, followed by the return and its caveats.

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 zero-required-param read-only referral-lookup tool with full schema coverage but no output schema, the description covers what's needed: status, return value, and limitations. A brief note on response shape would push it higher, but it's sufficient to invoke correctly.

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?

With 100% schema coverage the schema fully documents ph, days, and rigs including ranges, defaults, and override behavior. The description adds nothing about parameters, so baseline 3 applies.

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?

States a specific verb (returns where to rent instead) and resource (Galaxy Mind hashrate on MiningRigRentals), and distinguishes itself from siblings like get_quote and list_available_rigs by framing itself as a redirect/referral pointer. It's clear what it returns, though the name 'get_rental_quote' slightly misleads since it explicitly gives no price.

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?

Clearly signals the use case: direct rentals have closed, so use this to find where to rent instead. The 'gives no price and places no order' clause implicitly steers the agent away from expecting quote/order behavior, though it doesn't name a specific alternative sibling tool.

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