Crawlora MCP

usage_endpoints

Read-only

List per-endpoint usage rows with request and credit totals for the authenticated principal over a selected UTC range. Use usage_overview for the billing snapshot or usage_timeseries for changes over time.

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": "usage_endpoints"
  }
}

Input Schema

Name	Required	Description
`to`	No	Custom upper bound (RFC3339) when range=custom.
`from`	No	Custom lower bound (RFC3339) when range=custom.
`limit`	No	Maximum endpoints to return (clamps to 100).
`range`	No	Time range preset: period, day, week, month, or custom. Defaults to the current billing period.

Output Schema

Name	Required	Description	Default
`data`	Yes	The tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

First observedOct 5, 2026

TDQS

A4.2/5.0

Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds one genuine behavioral detail beyond the schema: that rows are scoped to the authenticated principal. It does not mention pagination or the limit clamp behavior, though those are partly in the schema.

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 purpose and scope are front-loaded and the disambiguation follows. Every sentence 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?

With an output schema present and full schema coverage, the description does not need to explain return values, and it covers purpose, scope, and alternatives adequately. Minor gap: it does not note default-range behavior or pagination expectations, which are only partially implied.

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 every parameter (to, from, limit, range) is already documented in the schema, including the limit clamp and range presets. The description adds no additional parameter meaning, so the baseline of 3 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?

States a specific verb (List) and resource (per-endpoint usage rows) with the exact contents (request and credit totals) and scope (authenticated principal, selected UTC range). It explicitly differentiates itself from sibling tools usage_overview and usage_timeseries, so an agent can route without opening a schema.

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

Usage Guidelines5/5

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

The second sentence names two alternative siblings and the condition each serves (billing snapshot vs. changes over time), which implicitly but clearly establishes when this per-endpoint listing is the right choice. This mirrors the calibration's high-scoring sibling-routing pattern.

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

All Crawlora MCP 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?