Skip to main content
Glama
Sign In
Crawlora MCP

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usage_endpoints

Get the current user's API endpoint usage breakdown by request volume, with credits, overage, and failed requests across preset or custom time ranges.

Instructions

Get current user's endpoint usage breakdown. Returns the signed-in user's usage broken down by endpoint, ordered by request volume. range is period (the current billing period, default), day, week, month or custom, which takes RFC3339 from and to. limit defaults to 20 (max 100). Each item has requests, charged_requests, failed_requests, non_billable_requests, credits and overage. Authenticated with a dashboard JWT.

Input Schema

NameRequiredDescriptionDefault
toNoCustom upper bound in RFC3339 format when range=custom
fromNoCustom lower bound in RFC3339 format when range=custom
limitNoMaximum endpoints to return. Defaults to 20 and clamps to 100.
rangeNoTime range preset. Defaults to the current billing period.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changedv1.17.5
    • addedInput schema / properties / range / enum
      Added value: +[
+  "period",
+  "day",
+  "week",
+  "month",
+  "custom"
+]
  2. Addedv1.1.0

TDQS

A3.8/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 authentication via dashboard JWT, default and maximum limits, ordering by request volume, valid range modes, and the exact per-item fields returned. It still omits pagination behavior and whether endpoints with zero usage are included, but overall it is substantially 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 a single dense paragraph that front-loads the core purpose and then supplies range, limit, return-field, and auth details in a logical order. Every sentence contributes useful information without filler.

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?

With no output schema and no annotations, the description does well by naming the returned fields and covering auth and limit constraints. It is nearly complete for a read-only usage tool, though it could still mention pagination or response ordering guarantees beyond 'ordered by request volume.'

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 description coverage is 100%, so the schema already documents all four parameters, including the custom from/to RFC3339 requirements, defaults, and limit clamping. The description reinforces those same details but adds little semantic meaning beyond the schema, so the baseline of 3 is appropriate.

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?

States a specific verb and resource: 'Get current user's endpoint usage breakdown' and adds that results are 'broken down by endpoint, ordered by request volume.' This clearly distinguishes it from broader siblings like usage_overview or usage_timeseries, though it does not explicitly name an alternative.

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

Usage Guidelines3/5

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

The description implies when to use it by describing the per-endpoint breakdown, but it never explicitly says when this tool is preferred over usage_overview, usage_timeseries, or usage_recent_ips. Usage context is present only through the range presets, not through alternative routing guidance.

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