Skip to main content
Glama

Start Rental Tool

start-rental-tool

Order phones by returning a Stripe Checkout link. Nothing is charged there: the link saves the user's card and holds one month per phone on it. The order then waits for an admin to assign concrete phones, and the held amount is charged when they are assigned, or earlier if an admin confirms the order can be fulfilled. Ask for one country with phones (plus an optional country), or spread the order across several with items. Requires accept_terms: true — before calling, show the user https://0bull.net/terms and https://0bull.net/privacy and get their agreement to them and to monthly renewal charges per assigned phone. Give the link to the user, then poll get-billing-tool to see the order and the phones arrive.

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": {
      "accept_terms": "<accept_terms>"
    },
    "name": "start-rental-tool"
  }
}

Input Schema

NameRequiredDescriptionDefault
itemsNoPhones per country, for an order spanning several: a list of {country, quantity} objects with any ISO 3166-1 alpha-2 country, at most 10 rows, 50 phones in total. Give this or `phones`.
phonesNoHow many phones to order in one country, 1 to 50. Give this or `items`.
countryNoISO-2 country for `phones`, e.g. ES, US or JP. Any ISO 3166-1 alpha-2 code. Defaults to ES.
accept_termsYesRequired, must be true. Before calling, show the user https://0bull.net/terms and https://0bull.net/privacy and get their agreement to them and to monthly renewal charges for each assigned phone until they cancel it.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior5/5

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

Annotations only say the tool is not read-only and not destructive; the description goes far beyond by explaining that nothing is charged at checkout, that a hold of one month per phone is placed, when the hold converts to a charge (on assignment, or earlier if an admin confirms fulfilment), and that monthly renewal charges follow until cancellation. It also discloses the delayed, admin-dependent side effect and the legal consent requirement before invocation — the kind of context an agent cannot get from structured fields.

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?

Five sentences, all functional, ordered as mechanism → charging behaviour → parameter choice → prerequisite → next step, which is a sensible front-loading of the most decision-relevant facts. The terms/privacy and renewal-charge wording is duplicated verbatim in the `accept_terms` schema description, so a sentence could be trimmed without loss.

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 mutating, multi-step purchase flow with no output schema, the description covers everything an agent needs: consent gating, parameter shaping, what the call returns (a checkout link to hand over), and how to verify progress via get-billing-tool. Nothing material about calling it correctly is missing.

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 100%, so the baseline is 3, but the description adds the decision logic behind the parameters: one country versus several, with `phones`/`country` and `items` presented as mutually exclusive strategies. The terms/consent wording is largely repeated from the `accept_terms` schema entry, so the added meaning is real but modest.

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 opening sentence gives a concrete verb and resource ('Order phones by returning a Stripe Checkout link') plus the distinctive payment mechanism (card saved, one month held per phone), which makes the tool easy to picture. It never names or contrasts a sibling such as request-phones-tool, so an agent must still infer whether that sibling is the alternative path for phone orders.

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?

It states exactly how to shape the call (single country via `phones` + optional `country`, or multi-country via `items`), the hard prerequisite (`accept_terms: true` with terms and privacy shown first), and the post-call workflow: hand the link to the user, then poll get-billing-tool. That names a concrete alternative/follow-up tool and the condition that selects it.

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