Skip to main content
Glama

quality_purchase_history

Read-onlyIdempotent

Read owned quality purchase snapshots, settlement mode and refund state. A pack sale is one purchase of 100 credits; sandbox purchases do not establish live revenue.

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": "quality_purchase_history"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.9/5.0
Behavior4/5

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

The annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the description is not burdened with safety disclosure. It adds genuinely non-obvious domain context: that a pack sale equals one purchase of 100 credits, and that sandbox purchases do not establish live revenue. It stops short of describing scope boundaries (e.g., whether it covers all owned purchases or a window) or result ordering.

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?

Two short sentences with no filler, and the core capability (what is read) is front-loaded before the clarifying domain notes. Every sentence carries information an agent would not get from the schema or annotations.

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

Completeness4/5

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

With no parameters, no output schema and full annotation coverage, the definition is nearly complete: it names the three classes of data returned (snapshots, settlement mode, refund state) and explains the credit/pack unit. What it omits is scope and volume expectations, which matter slightly since there is no output schema to describe result shape.

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, so there is no parameter meaning for the description to supply and the baseline of 4 applies. The description correctly avoids inventing filter or date-range options that the empty schema does not support.

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 uses a specific verb ("Read") and names concrete resources: owned quality purchase snapshots, settlement mode and refund state. An agent knows this is a read-only purchase/refund history lookup, but nothing in the text distinguishes it from closely related siblings such as quality_wallet or quality_billing_status.

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 implied rather than stated: 'purchase snapshots' and 'refund state' signal this is for auditing past purchases and refunds, and the sandbox/live-revenue caveat helps the agent interpret results. However, there is no explicit when-to-use or when-to-prefer-an-alternative guidance, and no prerequisite or scoping conditions are given.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.