Skip to main content
Glama

thrivecart_status

Verifies your Cotlet.dev account, credit balance and ThriveCart connection so you can confirm everything is ready before running order, product or reporting tasks.

Instructions

Check that your Cotlet.dev account and ThriveCart are ready: account, credits and ThriveCart connection.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.1.0

TDQS

B3.4/5.0
Behavior2/5

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

No annotations exist, so the description carries the full disclosure burden, yet it says nothing about whether this is read-only and side-effect free, whether it consumes credits, or what happens when a check fails (error vs. partial status). It does list the three things inspected, which is the only real behavioral signal.

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 front-loaded sentence with the enumerated checks at the end – no filler and nothing to trim, aside from a slightly awkward repetition of "account".

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 simple zero-param diagnostic, the description conveys the scope but there is no output schema, so it should have said what the response looks like (per-item statuses, error shape, or overall pass/fail). The failure behavior – a key thing an agent needs to decide next steps – is left unspecified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, which is the baseline-4 case; the description correctly signals a parameterless call by framing it as a global account/environment check.

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?

Names a specific verb ("Check") and enumerates exactly what is verified: the Cotlet.dev account, credits, and the ThriveCart connection. That makes it clearly a pre-flight readiness/diagnostic tool, though it never distinguishes itself from siblings like thrivecart_read or thrivecart_guide.

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 by the word "ready" and the word "Check" – an agent can infer this is a pre-flight/verification call, but there is no explicit when-to-use statement, no prerequisites, and no pointer to alternative tools if the check fails.

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