@crawlbrulee/mcp

Official

Overview Schema Source Related Servers Discussions Admin

Get current usage

usage

Check billing-cycle usage before large scrape jobs to confirm available credit. View total, used, and available credits, quota percent, max concurrency, and reset time.

Instructions

Return the current billing-cycle usage for the authenticated organization: total / used / available credits, used quota percent, max concurrency, and cycle reset time. Call this before launching large scrape jobs to confirm available credit.

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON Schema

Name	Required	Description
`usage_reset`	Yes	ISO 8601 UTC timestamp when the current billing cycle ends and used_credits resets.
`used_credits`	Yes	Credits spent so far in the current billing cycle. May exceed total_credits on plans that allow overages.
`total_credits`	Yes	Total credits available for the current billing cycle (plan base + purchased + gifted).
`max_concurrency`	Yes	Maximum number of concurrent jobs allowed for this organization (plan base + purchased + gifted extras).
`available_credits`	Yes	Remaining credits (max(0, total_credits - used_credits)). Clamped to 0 when in overage.
`used_quota_percent`	Yes	Percentage of total_credits used in the current cycle, rounded to 1 decimal. Not capped — values >100 indicate overage.

Schema Changelog

Changes observed during successful MCP inspections.

First observedv1.0.3Sep 25, 2026

TDQS

A4.5/5.0

Behavior4/5

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

With no annotations provided, the description carries the full behavioral burden. It clearly states that the tool returns usage data for the authenticated organization, lists the specific metrics, and implies a read-only operation. It does not discuss rate limits or authentication requirements, but the described behavior is transparent.

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 two sentences, front-loads the return content, and closes with a practical usage directive. Every sentence earns its place with no redundancy.

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 zero parameters, an output schema that documents return values, and a straightforward read operation, the description covers what the tool does, what it returns, and when to use it. Nothing essential is missing for an agent to invoke it correctly.

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, so the schema is trivially complete. The description adds no parameter-level detail because none is needed; the baseline of 4 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?

The description uses a specific verb ('Return') and names the exact resource ('current billing-cycle usage for the authenticated organization') with a detailed list of returned fields. It is clearly distinct from the sibling scraping tools and whoami.

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 explicitly tells the agent when to call this tool ('before launching large scrape jobs to confirm available credit'). It does not explicitly list exclusions or alternatives, but the context is clear enough for correct selection.

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

Deploy Server