Skip to main content
Glama

create_rental_checkout

Prepay a quoted rental by Stripe or crypto. For crypto provide payment_method=crypto, asset_id and buyer_wallet; follow the exact transfer instructions and verify the transaction. Unused crypto prepayment becomes reusable HOBO service credit; no automatic on-chain refund.

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": {
      "rental_id": "<rental_id>"
    },
    "name": "create_rental_checkout"
  }
}

Input Schema

NameRequiredDescriptionDefault
asset_idNo
rental_idYes
buyer_walletNo
payment_methodNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedInput schema / properties / asset_id
      Added value: +{
      +  "enum": [
      +    "ethereum_usdc",
      +    "base_usdc",
      +    "arbitrum_usdc",
      +    "optimism_usdc",
      +    "polygon_usdc",
      +    "linea_usdc",
      +    "sei_usdc",
      +    "arc_usdc",
      +    "ethereum_usds",
      +    "base_usds",
      +    "ethereum_eth",
      +    "base_eth",
      +    "arbitrum_eth",
      +    "optimism_eth",
      +    "bsc_bnb",
      +    "polygon_pol",
      +    "solana_sol",
      +    "bitcoin_btc"
      +  ],
      +  "type": "string"
      +}
    • addedInput schema / properties / buyer_wallet
      Added value: +{
      +  "type": "string"
      +}
    • addedInput schema / properties / payment_method
      Added value: +{
      +  "enum": [
      +    "stripe",
      +    "crypto"
      +  ],
      +  "type": "string"
      +}
  2. Added
  3. Removed
  4. Added

TDQS

A3.8/5.0
Behavior4/5

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that unused crypto prepayment converts to reusable HOBO service credit rather than being refunded on-chain, and that the agent must follow exact transfer instructions and then verify the transaction. This is real consequence-level information, though the Stripe path's behavior (redirect, expiry, failure modes) is left unstated.

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 sentences, front-loaded with the core action, then crypto requirements, then the refund/credit consequence. Every sentence adds information; no filler or repetition of the tool name.

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 payment-initiating tool with no annotations and no output schema, the definition covers the payment rails, the crypto-specific inputs, the post-transfer verification step, and the non-refundable credit policy. It omits what the call returns (checkout URL, invoice, or instructions) and any Stripe-path specifics, which an agent would likely want before invoking.

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 description must compensate, and it does for the conditional requirements: payment_method=crypto implies asset_id and buyer_wallet are needed, which the flat schema cannot express. It does not explain what rental_id must reference beyond 'quoted rental', nor whether asset_id must match the quoted currency/chain, leaving a gap on the enum's practical meaning.

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 states a specific verb and resource: 'Prepay a quoted rental by Stripe or crypto,' which tells an agent exactly what the tool does and that it covers both payment rails. It does not name sibling tools such as create_stripe_checkout or create_crypto_invoice, so differentiation from those must be inferred rather than read.

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

Usage Guidelines3/5

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

It implies a prerequisite ('a quoted rental') and gives conditional instructions for the crypto path (set payment_method=crypto with asset_id and buyer_wallet). It never states when to prefer this over the sibling payment tools, nor what to do if no quote exists yet, leaving routing and preconditions partly to inference.

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