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

A4.2/5.0
Behavior5/5

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

Annotations only say readOnlyHint=true and openWorldHint=false. The description goes well beyond them by disclosing the hard prerequisite (the download link from the purchase receipt containing session_id=cs_), that the order is re-verified as paid with Stripe on every call, and that only the kits included in that order are searched. That is exactly the kind of auth, per-call, and scoping behavior an agent needs before invoking.

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?

Three compact sentences, front-loaded with what is returned, then the prerequisite, then the verification behavior. The phrase 'with the list of files in their order' is slightly opaque, and it is punched in between two stronger clauses, which costs a bit of clarity.

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?

Output schema exists, so return values need not be explained. The description covers the prerequisite, the verification, and the search scoping, which is what matters for this tool. The one loose end is the unexplained mention of a file list returned alongside the passages, which leaves the response shape partly ambiguous.

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

Parameters4/5

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

Schema coverage is 100%, so the schema already documents both parameters and the baseline is 3. The description adds real meaning: it says what the order value physically is (the download link from the receipt) and, crucially, that it is used for per-call Stripe verification and to scope which kits are searched, which the schema does not state.

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 specific verb and resource: it returns passages from the kit and book documents a buyer owns, scoped to setup and how-to questions. The scope (only documents the buyer owns, only kits included in the paid order) is genuinely differentiating, though it never names a sibling such as kit_contents or search, leaving the agent to infer the boundary.

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 a clear usage condition: setup and how-to questions for a buyer, which implies it is the tool for post-purchase setup help rather than general search. It does not state exclusions, such as when to prefer kit_contents or generic search, so the guidance is clear but not complete.

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