Skip to main content
Glama

thrivecart_guide

Explains how to work in ThriveCart, including sign-in and the screens for transactions, products, checkouts, subscriptions, affiliates, and reports. Call it first for task guidance.

Instructions

How to work in ThriveCart (work with transactions, products, checkouts, subscriptions, affiliates and reports): its screens and the sign-in link. Call this first.

Tool call template

This tool declares no required parameters. Add optional parameters from the input schema as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {},
    "name": "thrivecart_guide"
  }
}

Input Schema

NameRequiredDescriptionDefault
taskNoWhat you want done in ThriveCart, in your words.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.6/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of disclosure. It does say what the tool returns (screens and the sign-in link), which implies a read-only informational response, but it does not explicitly state that it has no side effects, whether it requires a session, or what the response shape looks like.

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 short sentences, front-loaded with the resource and the domain list, ending with the actionable directive 'Call this first.' The parenthetical list is dense but earns its place by signaling scope; no filler sentences.

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 low-complexity, single-optional-parameter help tool with no output schema, the description covers what the tool is, what it contains, and when to invoke it. Only the return format and any auth/session expectations are left implicit.

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% for the single optional 'task' parameter, so the schema already explains that it accepts a free-text statement of intent. The description adds nothing about how to phrase the task or whether it is required, so baseline 3 applies.

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 resource — orientation content for ThriveCart's screens, sign-in link, and core domains (transactions, products, checkouts, subscriptions, affiliates, reports). It is clearly an informational guide rather than an action tool, though the verb is implicit rather than stated directly.

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?

'Call this first' gives an explicit ordering directive that positions this ahead of the action-oriented siblings (thrivecart_open, thrivecart_click, thrivecart_read). There are no explicit when-not-to-use conditions, but for an orientation tool the sequencing guidance is the key usage signal.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.