Skip to main content
Glama
Crawlora-org

Crawlora MCP

Official
by Crawlora-org
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

usage_endpoints

Retrieve your endpoint usage breakdown with request and credit totals per endpoint for a selected UTC time range, sorted by request volume.

Instructions

Get current user's endpoint usage breakdown. Returns per-endpoint request and credit totals for the selected UTC time range, ordered by request volume.

Input Schema

TableJSON 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

A4/5.0
Behavior3/5

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It adds useful behavior details: results are scoped to the current user, per-endpoint, limited to the selected time range, and sorted by request volume. However, it does not clarify read-only status, response shape beyond totals, or any edge cases, leaving moderate gaps.

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 with no filler. The first sentence states the action and scope, and the second clarifies the output format and ordering. Every word earns its place.

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?

The description covers the essential return content (per-endpoint request and credit totals, ordering) and the key scoping (current user, UTC time range). Given the simple schema and that parameters are fully described, only minor gaps remain, such as explicit differentiation from sibling usage tools and response structure details.

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 baseline is 3. The description reinforces the 'selected UTC time range' concept and adds ordering context, but it does not add meaning beyond the schema's parameter descriptions for range, from, to, or limit.

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?

States a specific verb ('Get'), a specific resource ('current user's endpoint usage breakdown'), and concrete return details (per-endpoint request/credit totals, ordering by request volume). This clearly distinguishes it from sibling tools like usage_overview, usage_timeseries, and usage_recent_ips.

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 provides clear context: this is for current-user endpoint-level usage over a selected UTC time range, which implies when it should be used. It does not explicitly name alternatives or exclusions, but the scope is specific enough for an agent to select it correctly.

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