Skip to main content
Glama

Order via an answer page slug

buy_by_answer

USE THIS when the human accepts the recommendation that came from an answer page. Order in one call by page slug instead of product id. Returns pay_url for the human to approve; no card is charged by the agent.

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": "buy_by_answer"
  }
}

Input Schema

NameRequiredDescriptionDefault
qtyNo
slugYes
buyerNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.5/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, so the safety profile is partly structured. The description adds genuinely useful behavior beyond that: it returns a pay_url for human approval and no card is charged by the agent, which clarifies the mutation is only an order draft. It does not describe order state, expiry of pay_url, or failure modes.

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 short sentences, front-loaded with the imperative 'USE THIS WHEN' trigger, followed by the mechanism and the outcome. Every sentence adds distinct information with no repetition of the title.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description conveys the core workflow, the key input, and the return behavior (pay_url, no charge), which is enough to select and invoke the tool. However, with no output schema and 0% parameter coverage, the undefined qty and buyer fields leave the invocation under-specified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters2/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must carry parameter meaning. It only explains slug as a page slug distinct from a product id; qty (default 1) and the nested buyer object with email and country are left entirely undocumented in both schema and description. That is a substantial gap for a 3-parameter tool with a nested object.

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?

States a concrete verb and resource ('Order in one call by page slug') and differentiates the lookup key from the product-id path, so the agent knows it operates on an answer page rather than a catalog item. It stops short of naming the sibling tool it replaces, but the resource and key are unambiguous.

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 an explicit trigger condition: 'USE THIS when the human accepts the recommendation that came from an answer page.' It also indicates the alternative key path ('instead of product id'), implying when to prefer another ordering tool. It does not name exclusions explicitly or state what to do if no answer page exists.

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