Skip to main content
Glama

thrivecart_click

Clicks a numbered element on the current ThriveCart page using the element number from the last page read, letting an AI agent interact with ThriveCart controls.

Instructions

Click a numbered element on the current ThriveCart page.

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": {
      "element": "<element>"
    },
    "name": "thrivecart_click"
  }
}

Input Schema

NameRequiredDescriptionDefault
elementYesElement number from the last read.

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?

With no annotations, the description carries the full behavioral burden and largely drops it: it doesn't say whether clicking navigates, submits, or mutates page state, whether element numbers are invalidated after the click, or what happens if the element is missing. Only the basic 'click something on the current page' behavior is conveyed.

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?

A single front-loaded sentence with no filler. Brevity is appropriate, though the space saved is not used to add any behavioral or sequencing detail.

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 state-changing browser-automation tool with no annotations and no output schema, the description should at minimum cover prerequisite ordering and what the click does to the page. Neither is present, leaving an agent to guess at sequencing and side effects.

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 schema itself explains the element number comes from the last read, so the description adds essentially nothing beyond the structured field. Baseline 3 is appropriate when the schema does the heavy lifting.

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 (click) and a specific target (a numbered element on the current ThriveCart page), which distinguishes it from siblings like thrivecart_type and thrivecart_read by action type. It stops short of naming how it differs from other interaction tools, but the action is unambiguous.

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: 'numbered element' combined with the schema note 'from the last read' hints that thrivecart_read must run first, but the description never says so explicitly and offers no when-not-use guidance or alternatives for interacting with non-numbered content.

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