Skip to main content
Glama

Get the order page address

get_selection_link
Read-onlyIdempotent

Returns the address of the Verateca order page for one of its three paid services (quick, full, review), with the price and currency the site shows for the country and a one-line description. The tool takes no payment and creates no order; the order page asks its own questions and takes payment there.

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": {
      "service": "<service>"
    },
    "name": "get_selection_link"
  }
}

Input Schema

NameRequiredDescriptionDefault
goalsNoOptional goals to preselect on the order page (quick: 1, full: up to 3; ignored for review). They travel sealed, not in plain words.
countryNoThe United States is the only market currently available.US
serviceYesquick: up to three products for one goal; full: one set for up to three goals; review: a written review by a Verateca specialist.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world behavior. The description adds useful behavioral context by stating no payment/order is created and that the order page handles its own questions and payment; it also previews returned price/currency/description. It stops short of detailing other runtime behavior such as error handling, so not a 5.

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?

Two sentences, front-loaded with the core return value and followed by a clarification that earns its place by preventing checkout misinterpretation. No redundant wording.

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 read-only link generator with a fully documented schema and no output schema, the description explains the main return content and the no-payment/no-order boundary. It is nearly complete, though it could better place the tool relative to the product-research siblings.

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 coverage is 100%, with service and country enums fully described and goals documented. The description repeats the three service names but adds little parameter-level meaning beyond the schema; baseline 3 applies.

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 uses a specific verb ('Returns') and resource ('address of the Verateca order page'), and scopes it to the three paid services. It also distinguishes the tool's role from a checkout action by noting it takes no payment and creates no order.

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 clarifies the tool's context (order-page link for one of three services) and rules out payment/order creation, but it does not explicitly say when to choose this over sibling product-information tools or name any alternative. Usage is implied rather than fully guided.

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