Skip to main content
Glama

Company Framework

Setup help for a buyer

buyer_setup_help
Read-only

Returns passages from the kit and book documents a buyer owns, for setup and how-to questions, with the list of files in their order. Requires the order: the download link from the purchase receipt, which contains session_id=cs_. The order is verified as paid with Stripe on each call and only the kits it includes are searched.

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": {
      "question": "<question>",
      "order": "<order>"
    },
    "name": "buyer_setup_help"
  }
}

Input Schema

NameRequiredDescriptionDefault
orderYesThe download link from their receipt, or the cs_ order id in it.
questionYesWhat they are stuck on.

Output Schema

NameRequiredDescriptionDefault
kitsYes
filesYes
passagesYes

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior4/5

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

Annotations already cover readOnly, closed-world, and non-destructive behavior, yet the description adds substantive context: the order must be verified as paid with Stripe on every call, and only kits included in that order are searched. This tells the agent about a per-call authorization check that could fail, which the annotations alone would not reveal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two sentences: the first states what is returned, the second states the required input and its provenance. Front-loaded and largely waste-free, with only a slightly awkward clause ('with the list of files in their order').

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?

The description covers what is searched, what constrains the search (order scope, Stripe verification), and what inputs are needed; return values are covered by the existing output schema. For a two-parameter read tool this is close to sufficient, with no remaining major gap.

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%, and the schema already explains both parameters, including the cs_ order id format. The description reinforces that the order is a download link from the receipt and is verified as paid, but adds little new meaning to the 'question' parameter beyond what the schema states.

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?

The description names a specific verb and resource — returns passages from the kit and book documents a buyer owns — and narrows the scope to setup and how-to questions, with the file list included. It is clearly distinct from generic tools like search or kit_contents, though it does not name those siblings explicitly.

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?

The phrase 'for setup and how-to questions' implies the triggering situation, and the requirement of an order (purchase receipt link) makes the prerequisite clear. However, there is no explicit statement of when to prefer this over alternatives such as search or kit_contents, nor any exclusion conditions.

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