Skip to main content
Glama
meshive-mcp

meshive-mcp

Official
by meshive

Show Billing History

billing_history
Read-onlyIdempotent

Retrieve money movements by kind: credits for top-ups and refunds, daily host earnings, or payouts with payout-account summary. Filter by date range to review pending earnings and account status.

Instructions

Show money movements: kind "credit" lists top-ups and refunds; "earnings" shows host earnings per day; "payouts" lists the payouts of a host's earnings (the last 90 days by default), with a summary of the payout account: whether it exists and is fully onboarded, and the earnings waiting to be paid out. since and until are dates in YYYY-MM-DD; amounts are USD and refunds are negative. Payouts are sent on their own once enough is waiting; setting up the payout account and its Stripe dashboard are in the console (Earnings), not here. For the current balance use the account tool instead.

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

Input Schema

NameRequiredDescriptionDefault
kindNocredit
limitNo
sinceNo
untilNo
cursorNo

Output Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description still adds real behavior: payouts default to the last 90 days, amounts are USD, refunds are negative, and payouts fire automatically when enough accrues. It does not discuss result ordering or how the cursor advances, which keeps it from a 5.

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?

The kind-by-kind mapping is front-loaded and scannable, and the format/currency notes are compressed into one line. The closing sentence about console setup is slightly long but genuinely prevents a wrong call path, so little is wasted.

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?

An output schema exists, so return shape needn't be explained, and the description covers mode semantics, defaults, and currency. The gaps are `limit`/`cursor` behavior for paging through long histories, which an agent would have to guess at.

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 0% and `kind` is a bare string with no enum, so the description's enumeration of "credit"/"earnings"/"payouts" is doing essential work, and it gives the date format and sign convention for `since`/`until`. However `limit` and `cursor` are never mentioned, so two of five parameters remain fully undocumented — significant for a paginated tool.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description opens with a specific verb+resource ("Show money movements") and then enumerates the three modes with what each returns. It explicitly contrasts itself with the `account` tool for the current balance, so an agent can distinguish it from the nearest sibling without opening a schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Each `kind` value is paired with the case it serves (top-ups/refunds vs. daily host earnings vs. outgoing payouts), and it names two alternatives: the console for payout-account/Stripe setup and the account tool for current balance. Exclusionary guidance is explicit.

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