My IP Help

Show my API usage

get_my_usage

Read-onlyIdempotent

The API key's plan, the lookups used and left this lookup month (single lookups plus bulk IPs), when the month resets, and the rate limit. Does not count as a lookup.

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

Input Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedNov 10, 2026

TDQS

A4.3/5.0

Behavior4/5

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered; the description contributes the non-obvious fact that this call is not billed against the lookup quota, which materially affects agent behavior. It also enumerates what is reported (plan, used, remaining, reset, rate limit) without covering error or edge cases such as exhausted quota.

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?

A single dense sentence listing exactly the values returned, with the most decision-relevant fact (this call is free) front-loaded as a closing caveat. Every clause corresponds to returned information; there is no filler.

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?

There is no output schema, and the description compensates by enumerating the fields an agent will receive, including the unit clarification that bulk IPs count within the same lookup total. For a zero-parameter read tool, nothing needed to call it correctly is missing.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool takes zero parameters, so there is nothing to disambiguate and the baseline of 4 applies. The description correctly implies the call is scoped implicitly to the calling API key rather than to any supplied identifier.

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?

The description names the exact resource and scope: the API key's plan, lookups used and remaining this lookup month, reset date, and rate limit. That is enough to distinguish it from the sibling lookup tools, and the closing clause 'Does not count as a lookup' reinforces that this is the metering tool, not a data lookup.

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?

Usage is implied rather than stated: an agent can infer it should call this to check quota or rate limits, and 'Does not count as a lookup' signals it is safe to call freely. There is no explicit when-to-use framing, no statement of prerequisites, and no named alternative for related quota questions.

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

All My IP Help 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?