Crawlora MCP

usage_timeseries

Read-only

Fetch chart-ready usage buckets for the JWT-authenticated API user. Use usage_overview for summary totals, usage_endpoints for endpoint breakdowns, or usage_recent_ips for recent client IPs.

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_timeseries"
  }
}

Input Schema

Name	Required	Description
`to`	No	Custom upper bound (RFC3339) when range=custom.
`from`	No	Custom lower bound (RFC3339) when range=custom.
`range`	No	Time range preset: period, day, week, month, or custom. Defaults to the current billing period.
`bucket`	No	Bucket size: hour or day.
`endpoint`	No	Optional endpoint filter, for example google/search.

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.5/5.0

Behavior4/5

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

Annotations supply readOnlyHint=true and openWorldHint=true, so safety is already covered. The description adds real context beyond that: results are scoped to the JWT-authenticated user and come back as 'chart-ready' buckets, which characterizes the output shape. It does not mention pagination or limits, but the output schema exists to carry return details.

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 waste: purpose first, then sibling routing. Every clause earns its place and the disambiguation is front-loaded after the core statement.

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?

With an output schema handling return values, 100% parameter coverage, and annotations covering safety, the description supplies what's missing: purpose, scope, and alternative-tool routing. Nothing an agent needs to select and call this correctly is absent.

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 range/bucket/to/from/endpoint are all documented in the schema. The description adds only an implicit hint that data is bucketed; it provides no syntax or format detail beyond the schema. Baseline 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 (fetch) and resource (usage buckets) plus scope qualifiers ('chart-ready', 'for the JWT-authenticated API user'). A reader immediately knows what this returns and whose data it covers, distinct from the sibling usage_* tools.

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?

Explicitly routes to three alternatives with the condition that selects each: usage_overview for summary totals, usage_endpoints for endpoint breakdowns, usage_recent_ips for recent client IPs. Nothing is left to inference about when to pick a different tool.

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?