PostRite

Get billing status and usage

get_billing_status

Read-only

Fetch the organization's plan, subscription status, post usage, and limits — and, for a subscription paid by Pix (subscription.paymentMethod: pix), the amount and deadlines of the invoice waiting to be paid. The Pix code itself is not returned: paying happens in the PostRite app, under Settings → Billing. Requires the organization owner role.

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

Input Schema

Name	Required	Description	Default
`organizationId`	No	Organization to act in — an id from list_organizations. Required when this connection was authorized for more than one organization; omit it when there is only one.

Output Schema

Name	Required	Description
`usage`	No	Counters for the current period
`limits`	No	The plan's limits
`isTrial`	No
`pixPayment`	No	The Pix that pays the open invoice of a subscription paid by Pix (`subscription.paymentMethod` is `pix`); null for card subscriptions and when nothing is owed. `dueAt` is when the organization is restricted if it stays unpaid; `payableUntil` is the invoice's due date, until which it can still be paid (paying lifts the restriction) and after which the subscription is canceled; `isExpired` means no code is payable any more and a new Pix must be generated. The Pix code and QR code are not returned here: the owner pays in the PostRite app, under Settings → Billing
`currentPrice`	No
`isAdminTrial`	No
`isIncomplete`	No
`isRestricted`	No
`subscription`	No
`isTrialExpired`	No
`isInGracePeriod`	No
`trialDaysRemaining`	No

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 5, 2026

TDQS

A4.4/5.0

Behavior5/5

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

Annotations only say this is a safe read; the description adds substantive context the agent cannot infer: an owner-role authorization requirement, an explicit exclusion (the Pix code is not returned), and a redirect to the app's Settings → Billing flow for payment. These are exactly the behavioral facts an agent needs before calling.

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?

Front-loaded with the core payload and then the conditional Pix detail; every clause carries information. The em-dash aside and inline field reference make it slightly dense, but nothing is redundant.

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

Completeness5/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 values need no explanation; the description instead covers the two things the schema cannot: the permission prerequisite and the Pix payment edge case with its non-returned field. Nothing an agent needs to call this correctly is missing.

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% and the organizationId schema text already explains the multi-organization vs. single-organization rule, which is the key semantic. The description only says 'the organization's' and adds no further meaning, so the baseline 3 applies.

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?

Uses a specific verb ('Fetch') with an enumerated resource list: plan, subscription status, post usage, limits, and Pix invoice details. This clearly separates it from siblings such as get_media_usage or get_analytics_summary, which cover different data domains.

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?

Gives a clear situational trigger (subscription paid via Pix) and states the required role ('organization owner'). It does not name an alternative tool for agents who lack that role or point to where billing changes are made beyond the in-app note, so it stops short of full when/when-not guidance.

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

All PostRite tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?