Skip to main content
Glama

Gilroy Motor — electric motorcycles (Chile)

Armar el enlace de compra

create_checkout_link
Read-onlyIdempotent

Arma un enlace que deja la moto o pack elegido (en el color elegido) en el carrito de gilroymotor.cl, listo para que la PERSONA pague con tarjeta (Flow) o transferencia. No compra, no paga y no reserva. Usa option_id de list_models, o model + color.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "create_checkout_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
colorNop. ej. negra, blanca, gris, roja, amarilla
modelNo
option_idNo

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=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds useful behavioral context beyond those annotations by clarifying that the link only prepares the cart, does not complete payment, does not reserve stock, and supports Flow card payment or bank transfer.

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?

The description is front-loaded, compact, and wastes no words. Three sentences cover the core action, the non-actions, and the parameter source pattern.

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 three-parameter link-building tool with no output schema, the description is largely complete: it explains the result, the cart behavior, payment options, and that no purchase or reservation occurs. It could say more about link lifetime, authentication, or precedence between option_id and model/color, but those are secondary gaps.

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 only 33%, so the description needs to compensate. It does explain that option_id comes from list_models and that model plus color is an alternative, but it does not clarify precedence when both option_id and model/color are supplied, nor does it fully document the model parameter.

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?

The description states a specific action and resource: it builds a link that places the chosen motorcycle or pack, in the chosen color, into the gilroymotor.cl cart. It also clarifies what the tool does not do (does not buy, pay, or reserve), which distinguishes it from a checkout or payment tool.

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?

The description gives clear usage context: use it to prepare a cart link for a person to pay by card via Flow or by transfer, and it explicitly says it does not purchase, pay, or reserve. It also points to list_models as the source for option_id, but it does not explicitly contrast against all sibling tools or state edge-case exclusions.

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