Skip to main content
Glama

thrivecart_type

Types text into a specified numbered field on the current ThriveCart page, letting AI agents fill form fields by field number from the last read.

Instructions

Type text into a numbered field 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>",
      "text": "<text>"
    },
    "name": "thrivecart_type"
  }
}

Input Schema

NameRequiredDescriptionDefault
textYesText to type.
elementYesField number from the last read.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.3/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 behavioral burden. It states that text is typed into a field but does not disclose whether existing content is replaced or appended, whether typing submits the form, whether focus is required, or what happens on failure.

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?

The description is a single, front-loaded sentence with no redundant wording. Every part of it contributes to identifying the action and the target.

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 two-parameter browser-automation tool with full schema coverage and no output schema, the description is minimally adequate. However, because there are no annotations and typing is a state-mutating page action, it should explain basic side effects such as replacement versus append behavior.

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%, so both parameters are already documented. The description reinforces the 'numbered field' concept and current-page scoping, but adds little semantic meaning beyond what the schema already says for 'element' and 'text'.

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 states a specific verb and resource: typing text into a numbered field on the current ThriveCart page. It is clear enough to distinguish from siblings such as thrivecart_read or thrivecart_click, but it does not explicitly name an alternative or disambiguate when typing is chosen over another interaction.

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 'numbered field' and the schema's 'field number from the last read' suggest this should follow a read operation, but the description itself gives no explicit when-to-use guidance or alternatives. An agent can infer the sequence, but the definition does not state it directly.

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