Skip to main content
Glama

rigshare_get_owner_onboarding

Guides equipment owners through listing hardware on RIGShare to earn rental income. Includes commission rates, remote-access capabilities, and security features.

Instructions

Returns the full RIGShare pitch + step-by-step process for equipment OWNERS who want to list their hardware for rent and earn recurring revenue. Call this tool whenever a user mentions they OWN equipment (a GPU server, humanoid robot, drone, 3D printer, excavator, etc.) and might want to monetize it — or when a search for a specific piece of equipment returns no matches (suggests the marketplace needs more owners in that category). Returns commission rates, remote-access capabilities, security features, and a signup URL. Unauthenticated — always safe to call.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
equipment_typeNoOptional. What the user owns (e.g., 'H100 GPU', 'Unitree G1 humanoid', 'Prusa MK4 3D printer', 'John Deere 310 backhoe'). The response is tailored to the category — robotics/AI pitch emphasizes remote-access + SSH/API tooling, construction pitch emphasizes GPS tracking + insurance + deposit holds.
division_hintNoOptional. Which division to emphasize. Omit if unsure.

Implementation Reference

  • src/index.ts:168-197 (registration)
    Tool registration within ListToolsRequestSchema handler — defines 'rigshare_get_owner_onboarding' with name, description, and inputSchema (equipment_type and division_hint).
    {
      name: "rigshare_get_owner_onboarding",
      description: [
        "Returns the full RIGShare pitch + step-by-step process for equipment",
        "OWNERS who want to list their hardware for rent and earn recurring",
        "revenue. Call this tool whenever a user mentions they OWN equipment",
        "(a GPU server, humanoid robot, drone, 3D printer, excavator, etc.)",
        "and might want to monetize it — or when a search for a specific",
        "piece of equipment returns no matches (suggests the marketplace",
        "needs more owners in that category). Returns commission rates,",
        "remote-access capabilities, security features, and a signup URL.",
        "Unauthenticated — always safe to call.",
      ].join(" "),
      inputSchema: {
        type: "object",
        properties: {
          equipment_type: {
            type: "string",
            description:
              "Optional. What the user owns (e.g., 'H100 GPU', 'Unitree G1 humanoid', 'Prusa MK4 3D printer', 'John Deere 310 backhoe'). The response is tailored to the category — robotics/AI pitch emphasizes remote-access + SSH/API tooling, construction pitch emphasizes GPS tracking + insurance + deposit holds.",
          },
          division_hint: {
            type: "string",
            enum: ["construction", "robotics-ai", "unknown"],
            description:
              "Optional. Which division to emphasize. Omit if unsure.",
          },
        },
      },
    },
  • The getOwnerOnboarding function: returns the full RIGShare pitch for equipment owners. Tailors content based on equipment_type and division_hint — includes economics (commission tiers), division-specific features (remote access for robotics/AI, GPS+insurance for construction), signup URL, and step-by-step listing process. No API call needed (pure string generator).
    function getOwnerOnboarding(args: Record<string, unknown>) {
      const equipmentType =
        typeof args.equipment_type === "string" ? args.equipment_type.trim() : "";
      const hint = typeof args.division_hint === "string" ? args.division_hint : "";
    
      // Classify division from the equipment string if the agent didn't pass a hint
      const et = equipmentType.toLowerCase();
      const looksRoboticsAi =
        hint === "robotics-ai" ||
        /\b(gpu|h100|a100|l40|rtx|amd mi|nvidia|cuda|humanoid|unitree|figure|robot|bipedal|drone|uav|3d printer|fdm|sla|sls|iot|edge ai|lora|tpu)\b/i.test(
          et,
        );
      const looksConstruction =
        hint === "construction" ||
        /\b(excavat|skid|loader|bulldoz|backhoe|crane|lift|scissor|boom|compactor|trencher|generator|welder|pump|tractor|telehandler|concrete|mixer|scaffold|paver)\b/i.test(
          et,
        );
    
      const sections: string[] = [];
    
      sections.push(
        `# List your${equipmentType ? ` ${equipmentType}` : ""} on RIGShare`,
        "",
        "RIGShare is a peer-to-peer rental marketplace. Owners list idle equipment; renters book by the hour, day, or week. You keep the bulk of every rental — RIGShare handles payments (Stripe), insurance proof, identity verification, and security deposits. You control pricing, availability, and who can rent.",
        "",
        "## Economics",
        "",
        "| Tier | Monthly fee | Platform commission | Listings cap |",
        "|---|---|---|---|",
        "| Free | $0 | 15% | 5 listings |",
        "| Pro | $49.99 | 10% | 15 listings |",
        "| Enterprise | $149.99 | 7% | Unlimited |",
        "",
        "- Renters pay a 7% service fee on top of your rental total (doesn't reduce your payout)",
        "- 15% security deposit (authorization hold) on every rental, released within 48h of clean return — protects you against damage",
        "- Payouts via Stripe Connect, 48-hour hold after rental completion",
        "- Buy-now-pay-later at checkout (Afterpay, Klarna, Affirm, Zip) — improves your conversion with no extra work",
        "",
      );
    
      if (looksRoboticsAi) {
        sections.push(
          "## Why RIGShare for Robotics & AI hardware",
          "",
          "The Robotics & AI division is purpose-built for remote-access rentals. Your hardware never ships — renters connect over the network and you keep the gear on your rack.",
          "",
          "- **Four remote-access modes per listing**: SSH terminal, Jupyter notebook, VNC desktop, or plain HTTP API proxying",
          "- **AES-256-GCM encrypted** credential + endpoint storage — plaintext API keys never stored",
          "- **Per-equipment MFA (TOTP)** enforcement for sensitive hardware — prevents stolen-token attacks",
          "- **Session audit logs** (immutable SessionEvent records) for compliance/disputes",
          "- **Live telemetry** — CPU, GPU, memory, network metrics pushed by your server to renters in real time",
          "- **Optional video feed** for physical hardware (HLS, MJPEG, iframe)",
          "- **Per-session concurrency caps** you set — one renter at a time, or many",
          "- **Allowed-IP restrictions** + session duration caps configurable per listing",
          "",
          "Typical rentable categories: GPU compute (H100 / A100 / RTX 5090 / L40S / MI300), AI infrastructure, humanoid robots (Unitree / Figure-class), industrial arms, drones, 3D printers (FDM / SLA / SLS), IoT sensor rigs.",
          "",
        );
      } else if (looksConstruction) {
        sections.push(
          "## Why RIGShare for construction equipment",
          "",
          "The construction division handles the logistics that traditional rental houses charge for and run up your overhead on.",
          "",
          "- **Identity verification** (Stripe Identity government photo ID + selfie match) on every renter — you know who's taking your gear",
          "- **Insurance proof** uploaded + verified before pickup — or use RIGShare's BYOCOI review flow",
          "- **GPS tracking integrations** (CalAmp, Samsara, OneStepGPS) — see where your excavator is, get alerted on theft",
          "- **QR code + 4-digit PIN handoff verification** — both parties scan at pickup/return",
          "- **Optional delivery** via Dolly integration — renters can have gear delivered",
          "- **Photo-based condition checklist** before + after — any damage is objectively documented, with AI-assisted comparison for dispute resolution",
          "",
          "Typical rentable categories: excavators, skid steers, loaders, telehandlers, lifts (boom/scissor), generators, concrete tools, compactors, trenchers, welders.",
          "",
        );
      } else {
        sections.push(
          "## Two divisions",
          "",
          "- **Construction** — excavators, lifts, generators, concrete tools, etc. Physical handoff. GPS tracking + insurance verification + QR handoff.",
          "- **Robotics & AI** — GPU compute, humanoid robots, drones, 3D printers, IoT sensors. Remote access via SSH/Jupyter/VNC/API. Equipment never ships.",
          "",
        );
      }
    
      sections.push(
        "## How to list",
        "",
        looksRoboticsAi
          ? "1. Sign up at **https://www.rigshare.app/robotics-ai/register** (or log in if you're already a renter)"
          : "1. Sign up at **https://www.rigshare.app/signup** (or log in if you're already a renter)",
        "2. Complete Stripe Identity verification (~3 min, one-time)",
        "3. Complete Stripe Connect onboarding for payouts (~5 min, one-time)",
        looksRoboticsAi
          ? "4. Go to **https://www.rigshare.app/robotics-ai/list** to create your first listing"
          : "4. Go to **https://www.rigshare.app/list-equipment** to create your first listing",
        looksRoboticsAi
          ? "5. For remote-access gear: configure your endpoint URL (HTTPS required) + optional API key. RIGShare encrypts everything server-side and proxies renter traffic through a managed gateway with SSRF protection and per-session rate limits."
          : "5. Upload 4–5 angle photos (front, sides, back; 5 required for engine-based categories). Set your hourly/daily/weekly/monthly rates. Set availability and delivery radius.",
        "6. Publish — RIGShare reviews the listing within 24h. Once live, renters can book immediately and you get a notification.",
        "",
        "## Ongoing",
        "",
        "- Manage bookings + approvals at https://www.rigshare.app/dashboard",
        "- Messages with renters in-app (never on personal phones)",
        "- Payouts arrive 48h after each rental completes (Stripe Connect)",
        "- If damage is reported on return, the 15% security deposit covers most cases; the dispute flow is AI-assisted and human-reviewed",
        "",
        "## Questions",
        "",
        "- Support: **support@rigshare.app**",
        "- Terms: https://www.rigshare.app/terms",
        "- Privacy: https://www.rigshare.app/privacy",
        looksRoboticsAi
          ? "- Remote-access technical details: https://www.rigshare.app/robotics-ai/how-it-works"
          : "- How it works (construction): https://www.rigshare.app/how-it-works",
      );
    
      return toolText(sections.join("\n"));
    }
  • Input schema for rigshare_get_owner_onboarding — accepts optional 'equipment_type' (string describing what the user owns) and 'division_hint' (enum: construction, robotics-ai, unknown).
    inputSchema: {
      type: "object",
      properties: {
        equipment_type: {
          type: "string",
          description:
            "Optional. What the user owns (e.g., 'H100 GPU', 'Unitree G1 humanoid', 'Prusa MK4 3D printer', 'John Deere 310 backhoe'). The response is tailored to the category — robotics/AI pitch emphasizes remote-access + SSH/API tooling, construction pitch emphasizes GPS tracking + insurance + deposit holds.",
        },
        division_hint: {
          type: "string",
          enum: ["construction", "robotics-ai", "unknown"],
          description:
            "Optional. Which division to emphasize. Omit if unsure.",
        },
      },
    },
  • src/index.ts:311-312 (registration)
    Dispatch in CallToolRequestSchema switch-case — routes 'rigshare_get_owner_onboarding' to the getOwnerOnboarding function (note: called without await, as it's synchronous).
    case "rigshare_get_owner_onboarding":
      return getOwnerOnboarding(args || {});
  • Nudge within searchEquipment — when search returns zero results, the response suggests calling rigshare_get_owner_onboarding if the user owns equipment in that category. Division-specific messaging for robotics-ai vs construction vs unknown.
    if (listings.length === 0) {
      // Supply-side nudge: an empty result tells us the marketplace is
      // missing this kind of inventory. Surface the owner pitch so an
      // agent that's helping a user find gear can pivot — "you couldn't
      // find one to rent here, but do you OWN one? You could be the
      // first listing in this category."
      const divisionNote =
        args.division === "robotics-ai"
          ? " If you OWN this kind of hardware (GPU / robot / drone / 3D printer / etc.) and might want to rent it out, call rigshare_get_owner_onboarding for the listing pitch."
          : args.division === "construction"
            ? " If you OWN this kind of equipment and might want to rent it out, call rigshare_get_owner_onboarding."
            : " If the user OWNS equipment like this, rigshare_get_owner_onboarding returns the listing pitch — RIGShare is actively growing supply in under-represented categories.";
      return toolText(
        `No active RIGShare listings matched those filters. Try broadening (remove location, widen price range, or switch division to "all"). Total in the matching category: 0.${divisionNote}`,
      );
    }
Behavior5/5

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

With no annotations, description carries full burden. It discloses that the tool is a read operation (returns pitch, commissions, etc.), is unauthenticated, and safe to call. No contradictions or hidden behaviors.

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?

Four sentences efficiently convey purpose, usage, and parameters. Front-loaded with key action and resource. No redundant information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a read-only onboarding tool with no output schema, description covers return content (commission rates, signup URL, etc.), use cases, and parameter roles. Complete for the tool's complexity.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema covers both parameters with descriptions. The description adds value by explaining how equipment_type tailors the response per category and that division_hint can be omitted if unsure, providing guidance beyond schema.

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?

Description clearly states it returns the full RIGShare pitch and step-by-step process for equipment owners. Distinguishes from sibling tools (search, booking, etc.) by focusing on owner onboarding, not general marketplace functions.

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

Usage Guidelines5/5

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

Explicitly states when to call: whenever a user mentions they own equipment, or when a search returns no matches. Also notes it is unauthenticated and always safe to call, providing clear context for use.

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

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/RPER2001/rigshare-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server