Skip to main content
Glama

thrivecart_open

Opens a ThriveCart page in your signed-in Cloud Browser so you can manage transactions, products, checkouts, subscriptions, affiliates, and reports.

Instructions

Open a ThriveCart page in your signed-in Cloud Browser (default https://thrivecart.com) to work with work with transactions, products, checkouts, subscriptions, affiliates and reports.

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_open"
  }
}

Input Schema

NameRequiredDescriptionDefault
urlNoPage to open. Default: https://thrivecart.com

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.1/5.0
Behavior2/5

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

No annotations are provided, so the description carries the full burden. It does add one valuable behavioral fact — the browser is signed-in, implying an authenticated session — but says nothing about whether it opens a new tab, navigates the existing page, what happens to prior page state, or what a success response 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?

One front-loaded sentence with the default URL placed early, but it contains a literal duplication ("to work with work with") that wastes words and reads as unpolished.

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

Completeness2/5

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

For a simple one-optional-parameter tool this is close, but with zero annotations and no output schema the description should clarify session/navigation behavior and what the agent can expect after opening — none of which is covered.

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 coverage is 100% and the single url parameter is already documented with its default, so the description merely repeats that default rather than adding format, path, or validation semantics. 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?

Clear verb+resource: "Open a ThriveCart page in your signed-in Cloud Browser," with a named default URL. It implicitly distinguishes navigation from sibling operations like thrivecart_read and thrivecart_click by framing the tool as page-opening, though it never names them.

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 only implied: the phrase "to work with transactions, products, checkouts, subscriptions, affiliates and reports" hints this is a prerequisite step before read/click actions, but no explicit when-to-use, when-not-to-use, or alternative routing is given.

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