Skip to main content
Glama

Get purchase options

get_purchase_options
Read-onlyIdempotent

Return dated official and affiliate buying links recorded by Valumech for one robot. This never opens a retailer, submits data, adds to cart, or purchases.

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": {
      "robot": "<robot>"
    },
    "name": "get_purchase_options"
  }
}

Input Schema

NameRequiredDescriptionDefault
robotYesCatalog ID or a sufficiently specific maker and model name.
regionNoBuyer region. The first pilot currently supports US offers.US

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 readOnlyHint/idempotentHint/destructiveHint=false, but the description adds concrete behavioral context beyond them: it never opens a retailer, submits data, adds to cart, or purchases. That is a useful, specific guarantee about external side effects, though it doesn't cover freshness/latency of the recorded links.

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, zero filler, with the core purpose in the first sentence and the safety boundary immediately after. Nothing is buried or repeated.

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?

There is no output schema, so the description must carry the return shape; 'dated official and affiliate buying links' does outline the payload, but it omits items such as whether prices or availability are included and how many links to expect. Combined with rich annotations and full schema coverage, this is nearly complete.

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%, so the robot ID/name and region enum are already documented in the schema. The description only surfaces that one robot is targeted per call and adds nothing about the region parameter, so 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?

States a specific verb and resource: 'Return dated official and affiliate buying links recorded by Valumech for one robot.' The scope (one robot's buying links) is distinct from sibling tools like get_robot_price and search_robot_catalog, so an agent can route without opening a schema.

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?

Usage is implied by the resource ('buying links' rather than prices or specs), and the second sentence clarifies the tool is purely informational. However, it never explicitly says when to prefer this over get_robot_price or the other siblings, so routing remains partly inferential.

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