postmoderno

Get plan usage

get_usage

Read-onlyIdempotent

Show how much of the workspace's plan is used and how much is left: each limit's used, max and left, and the wallet for paid platforms. For questions about what is left, and before planning a batch of posts. posts_per_month counts deliveries sent or booked for this UTC month (one post to three accounts is three) and starts again at resets_at_utc. The rest count what exists now: scheduled_posts the posts and replies waiting to go out, workspaces every workspace the same billing account pays for, connected_accounts those not on hold, members, context_documents (writing notes of every kind, from voice to learnings), series not archived, media_storage_bytes the images and video stored by every workspace on the billing account, and media_upload_bytes_per_month the media that account sent this UTC month, deleted files included, which starts again at resets_at_utc. posts_per_thread caps each thread, a post with its replies, and counts nothing; a platform's own cap may be lower. near_limit marks a limit four-fifths used (never a limit of one, which is the plan's shape), and full one with no room left. The wallet is shared by every workspace on the same billing account (shared_by_workspaces) and counted in posts, never dollars.

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description	Default
`plan`	Yes
`limits`	Yes
`wallet`	No
`month_utc`	Yes
`plan_name`	Yes

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 7, 2026

TDQS

A4.6/5.0

Behavior5/5

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

Annotations already declare a safe, idempotent, closed-world read, so the bar is lower. The description still adds substantial behavioral context: reset semantics (resets_at_utc), counting rules (one post to three accounts is three; deleted files included), near_limit and full thresholds, and wallet sharing across workspaces. This is exactly the interpretive detail an agent needs beyond structured fields.

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 description is dense and long, but it is front-loaded with purpose and usage before defining each counter. Every clause carries semantic weight, though the single-paragraph format could be made more scannable with light structuring.

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?

Given the tool's complexity (many plan counters), the presence of an output schema, and the zero-parameter interface, the description is complete enough for correct invocation. It explains the meaning of every counter and the wallet, leaving no major interpretive gap.

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 has zero parameters, and the schema description coverage is 100%, so there is no parameter meaning to add. The baseline for a no-param tool is 4, which is appropriate here.

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 and resource: 'Show how much of the workspace's plan is used and how much is left.' It enumerates the exact counters returned (used, max, left, wallet), so an agent knows precisely what the tool does and can distinguish it from any sibling.

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?

It gives explicit when-to-use guidance: 'For questions about what is left, and before planning a batch of posts.' No direct alternative tool is named, but no sibling provides plan usage, so there is no ambiguity to resolve.

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

All postmoderno 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?