Skip to main content
Glama
platformtaxhub-hash

platformtaxhub-mcp

by platformtaxhub-hash
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Platform Payout Calendar

platform_payout_calendar

Find out when a platform's next payout will be initiated and when it will arrive in your bank account, with regional transfer delays and weekend rollovers applied.

Instructions

Given one or more platforms, returns when their next payout is expected to be initiated and when it should actually arrive in your bank account (payout date plus regional bank-transfer delay, pushed off weekends). Mirrors platformincome.com/platform-payout-calendar.html exactly, using the same live data source. Call list_payout_platforms first if you don't already know a platform's id.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
monthNoMonth to check, as YYYY-MM (e.g. '2026-10'), for looking up a specific past or future month. If omitted, the tool instead returns each platform's actual NEXT upcoming payout (rolling forward past any already-happened date in the current month).
regionNoRegion, used for the default bank-transfer delay when a platform doesn't publish its own. Defaults to 'int' (International, 5 days).int
platformIdsYesOne or more platform ids, e.g. ['youtube', 'upwork', 'airbnb']. Call list_payout_platforms to see all valid ids.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.3.0

TDQS

A4.4/5.0
Behavior4/5

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

No annotations are provided, so the description carries the full burden. It discloses behavior beyond a simple 'returns dates': actual arrival is computed with regional delay and weekends pushed off, and it mirrors a live data source. It does not cover error handling or rate limits, but for a read-only lookup the key behaviors are explained.

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 three sentences with no filler. It front-loads the core purpose, adds a source-mirroring note, and closes with an actionable prerequisite. Every sentence earns its place.

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?

Without an output schema, the description clearly explains what the tool returns: payout initiation and actual arrival dates. Combined with the fully described input schema, an agent has enough to call the tool correctly. It could be more explicit about response shape or multi-platform behavior, but the prose covers the essential return semantics.

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?

Schema coverage is 100%, giving a baseline of 3. The description adds meaning beyond the schema by explaining that the arrival date includes regional bank-transfer delay and weekend adjustment, and by telling the agent to call list_payout_platforms for valid ids. This enriches the platformIds and region parameters without repeating the schema verbatim.

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 clearly states the specific verb and resource: given platforms, it returns next payout initiation and actual arrival dates, including regional bank-transfer delay and weekend handling. It also distinguishes itself from sibling tools by focusing on payout scheduling rather than benefits or take-home pay calculations.

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

Usage Guidelines4/5

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

The description gives clear context on when to use the tool and provides a prerequisite: call list_payout_platforms first if the platform id is unknown. It does not explicitly name alternatives or exclusions, but the usage context is clear and actionable.

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

Deploy Server

Other Tools