Skip to main content
Glama
Sign In

GlobalHostia

by com.globalhostia
OverviewDiscussionsAdmin

Build a cart link

build_cart_link
Read-onlyIdempotent

Ready-to-pay cart deep link for one plan with the billing cycle and currency preselected, optionally attaching a domain to the hosting order. Returns the exact price and setup fee for that cycle. Give the link to the customer to finish checkout. To register a new domain, use the link from check_domain (domainOnlyCartUrl is also returned).

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": {
      "slug": "<slug>"
    },
    "name": "build_cart_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
slugYesProduct slug as returned by search_products, recommend_plan or list_categories.
domainNoOptional domain to use with the hosting plan, e.g. mybrand.com.
currencyNoISO 4217 currency code, e.g. USD or AED. Defaults to USD. An unsupported code returns an error listing the valid ones.
billing_cycleNoBilling cycle; must be one the plan offers (see get_product). Defaults to monthly when offered, else the shortest cycle.

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, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds value beyond annotations by explaining that the result is a hand-off link for the customer and that the response includes the exact price and setup fee for the chosen cycle. It does not spell out failure behavior (e.g. what happens on an unsupported plan/cycle combination) beyond what the schema notes.

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?

Three sentences, front-loaded with the purpose, then the hand-off instruction, then the domain alternative. Every sentence carries distinct information with no restatement of the name or schema.

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?

With no output schema, the description partially compensates by naming the returned price and setup fee, and the usage sentence implies a cart URL plus domainOnlyCartUrl. It is sufficient for a 4-parameter, single-purpose link builder, though a full enumeration of returned fields would make it airtight.

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?

Schema description coverage is 100%, with slug, domain, currency and billing_cycle all documented including the enum and defaults, so the baseline is 3. The description adds modest meaning by framing the domain as attached to the hosting order and noting that cycle/currency are preselected into the link, but it adds no syntax or format detail beyond the 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?

States a specific verb and artifact ('build a ready-to-pay cart deep link for one plan') plus the scope of what is preselected (billing cycle, currency, optional domain) and what it returns (price and setup fee). An agent can separate this from get_order_link or check_domain without opening any 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?

Gives clear operating context: 'Give the link to the customer to finish checkout', and names the alternative path for domain registration via check_domain. It does not explicitly state when to prefer this over get_order_link or when not to build a link at all (e.g. before comparing plans), so it stops short of full when/when-not coverage.

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

All GlobalHostia toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources