Skip to main content
Glama
Sign In

Crawlora MCP

by net.crawlora
OverviewDiscussionsAdmin

usage_recent_ips

Read-only

List recent client IP items observed for the JWT-authenticated user's product API traffic, ordered by last seen. range selects a preset or custom window (from and to use RFC3339); the default is the current billing period and results cap at 100. Use usage_overview for aggregates, usage_endpoints for route counts, or usage_timeseries for trends.

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

Input Schema

NameRequiredDescriptionDefault
toNoCustom upper bound (RFC3339) when range=custom.
fromNoCustom lower bound (RFC3339) when range=custom.
limitNoMaximum IPs to return (clamps to 100).
rangeNoTime range preset: period, day, week, month, or custom. Defaults to the current billing period.

Output Schema

NameRequiredDescriptionDefault
dataYesThe tool result payload (shape varies per tool; see each tool's docs resource).

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.5/5.0
Behavior4/5

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

Annotations only declare readOnlyHint and openWorldHint; the description adds meaningful behavior beyond that: JWT-scoped user traffic, ordering by last seen, the default billing period, and the 100-result cap. It stops short of noting auth prerequisites or pagination beyond the cap, so not quite perfect.

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 zero waste: the first defines the resource and scope, the second bundles range/default/cap behavior and the sibling routing. Front-loaded and dense without padding.

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?

An output schema exists, so return shape need not be explained. The description covers scope, ordering, defaults, cap, and sibling alternatives, which is everything needed to select and call the tool correctly.

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 from/to as RFC3339 custom bounds, the range presets, and the 100 clamp. The description restates range semantics and adds the default window, which is marginal value over structured data. Baseline 3 is appropriate.

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 (recent client IP items), with scope qualifiers (JWT-authenticated user, product API traffic) and ordering (by last seen). It explicitly names sibling tools it is not, so an agent can distinguish it without opening schemas.

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?

Directly routes the agent: 'Use usage_overview for aggregates, usage_endpoints for route counts, or usage_timeseries for trends.' Combined with the default window statement, the when/when-not is fully explicit.

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

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