Skip to main content
Glama
Sign In
crawlbrulee

crawlbrulee-mcp

Official
by crawlbrulee
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Get current usage

usage

Check your organization's current billing-cycle credits, quota percentage, concurrency limit, and reset time before launching large scrape jobs.

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

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
usage_resetYesISO 8601 UTC timestamp when the current billing cycle ends and used_credits resets.
used_creditsYesCredits spent so far in the current billing cycle. May exceed total_credits on plans that allow overages.
total_creditsYesTotal credits available for the current billing cycle (plan base + purchased + gifted).
max_concurrencyYesMaximum number of concurrent jobs allowed for this organization (plan base + purchased + gifted extras).
available_creditsYesRemaining credits (max(0, total_credits - used_credits)). Clamped to 0 when in overage.
used_quota_percentYesPercentage 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.

  1. Changed1 schema field changedv1.3.3
    • changedOutput schema / properties / usage_reset / pattern
      Previous value: -"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d(?::[0-5]\\d(?:\\.\\d+)?)?(?:Z))$"New value: +"^(?:(?:\\d\\d[2468][048]|\\d\\d[13579][26]|\\d\\d0[48]|[02468][048]00|[13579][26]00)-02-29|\\d{4}-(?:(?:0[13578]|1[02])-(?:0[1-9]|[12]\\d|3[01])|(?:0[469]|11)-(?:0[1-9]|[12]\\d|30)|(?:02)-(?:0[1-9]|1\\d|2[0-8])))T(?:(?:[01]\\d|2[0-3]):[0-5]\\d:[0-5]\\d(?:\\.\\d+)?(?:Z))$"
  2. First observedv1.0.3

TDQS

A3.9/5.0
Behavior3/5

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

With no annotations, the description carries full behavioral burden. 'Return' and 'authenticated organization' imply a read-only, org-scoped call with implicit auth, but it never states that it has no side effects, whether results are cached, or any rate/limit behavior. Adequate but not rich.

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?

Two sentences, front-loaded with what is returned, followed by the one actionable usage cue. No filler or restatement of the title.

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 enumerating return fields is a bonus rather than a necessity, and 0 params keep the call simple. The only real gap is not contrasting this with whoami for agents deciding which introspection tool to call.

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?

Zero parameters, so there is nothing for the description to disambiguate; the baseline for a parameterless tool applies. The description correctly implies no inputs are needed and implicitly scopes the call to the authenticated org.

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

Purpose4/5

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

Names a specific resource (billing-cycle usage for the authenticated organization) and enumerates the exact fields returned (credits, used percent, max concurrency, reset time). It is not confused with the scrape* or map siblings, though it never explicitly names whoami as a near-neighbor that also reports on the caller.

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 concrete triggering condition: call before launching large scrape jobs to confirm available credit. That ties it directly to the scrape siblings. It stops short of stating when not to call it (e.g., it's unnecessary for small jobs or for per-user checks).

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