Skip to main content
Glama

thrivecart_read

Read the current ThriveCart page to capture visible text and numbered buttons, links, and fields, optionally limited to a specific element.

Instructions

Read the current ThriveCart page: its text and numbered buttons, links and fields.

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

Input Schema

NameRequiredDescriptionDefault
elementNoRead only inside this element.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

A3.5/5.0
Behavior3/5

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

With no annotations at all, the description carries the full burden, and it does establish that this is a non-mutating read that surfaces text, buttons, links and fields. It does not disclose whether the snapshot covers the whole page or only the viewport, whether output is truncated for large pages, or that the "numbered" indices are what the click/type siblings consume.

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

Conciseness5/5

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

A single tight sentence with the action front-loaded and the returned content listed afterward. Every clause carries information; nothing is redundant.

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

Completeness3/5

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

For a one-parameter read tool with no annotations, the description covers what is returned at a high level, which is the most important thing. However, with no output schema, the shape of the result, the significance of the numbered buttons for later click/type calls, and any size limits remain undescribed.

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 optional parameter is documented in the schema as "Read only inside this element." The description adds nothing about element scoping, which the schema already covers, 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?

"Read the current ThriveCart page" gives a specific verb and resource, and the enumeration of text, numbered buttons, links and fields tells the agent exactly what comes back. It is distinguishable from siblings like thrivecart_click and thrivecart_type by being purely observational, though it never names an alternative 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?

Usage is only implied: an agent can infer this is the way to inspect the page before clicking or typing. There is no explicit "use this when..." statement, no mention of prerequisites such as requiring an open page, and no guidance on when thrivecart_status would be preferred instead.

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