Leadgen ONRC Romania

Show my daily allowance

get_usage

Read-onlyIdempotent

Show your own allowance: plan, daily limit, lookups used today, how many remain, when it resets (00:00 UTC (02:00 or 03:00 in Romania)) and any credit balance. Free and never counted as a lookup. Limits: 30 anonymous MCP calls a day, 50 with a free API key from https://leadgen.adrianhomelab.com/start (an email address, no payment).

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

Input Schema

Name	Required	Description	Default
No arguments

Output Schema

Name	Required	Description
`plan`	No	Plan name (free, pro, business).
`error`	No	Set only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.
`links`	No	get_a_key, pricing, docs.
`counted`	No	Always false: this call is not counted.
`message`	No	A sentence for the caller.
`identity`	No	Who is counted: kind (key or anonymous) and counted_as.
`remaining`	No	Lookups left today.
`resets_at`	No	When the allowance resets (ISO 8601, 00:00 UTC).
`suspended`	No	true when the key is suspended.
`used_today`	No	Lookups used today.
`daily_limit`	No	Lookups allowed per UTC day.
`entitlements`	No	What the plan includes.
`resets_in_seconds`	No	Seconds until the reset.

Schema Changelog

Changes observed during successful MCP inspections.

Changed1 schema field changedOct 17, 2026

changedOutput schema / (root)

Previous value: -nullNew value: +{
+  "additionalProperties": true,
+  "description": "Your plan, daily allowance and what is left today.",
+  "properties": {
+    "counted": {
+      "description": "Always false: this call is not counted.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "daily_limit": {
+      "description": "Lookups allowed per UTC day.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "entitlements": {
+      "description": "What the plan includes.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "error": {
+      "description": "Set only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "identity": {
+      "description": "Who is counted: kind (key or anonymous) and counted_as.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "links": {
+      "description": "get_a_key, pricing, docs.",
+      "type": [
+        "object",
+        "null"
+      ]
+    },
+    "message": {
+      "description": "A sentence for the caller.",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "plan": {
+      "description": "Plan name (free, pro, business).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "remaining": {
+      "description": "Lookups left today.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "resets_at": {
+      "description": "When the allowance resets (ISO 8601, 00:00 UTC).",
+      "type": [
+        "string",
+        "null"
+      ]
+    },
+    "resets_in_seconds": {
+      "description": "Seconds until the reset.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    },
+    "suspended": {
+      "description": "true when the key is suspended.",
+      "type": [
+        "boolean",
+        "null"
+      ]
+    },
+    "used_today": {
+      "description": "Lookups used today.",
+      "type": [
+        "integer",
+        "null"
+      ]
+    }
+  },
+  "type": "object"
+}

AddedOct 15, 2026

TDQS

A4.7/5.0

Behavior5/5

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

Annotations already establish that this is a safe, read-only, idempotent status check. The description adds substantial behavioral context beyond that: it is free, never counted as a lookup, resets at 00:00 UTC, and has rate limits of 30 anonymous calls/day or 50 with a free API key.

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?

The description is front-loaded with the core purpose, then efficiently adds reset timing, cost behavior, and rate limits. Every clause contributes useful operational context without unnecessary repetition.

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?

Given the zero-parameter schema, rich annotations, and existing output schema, the definition is complete enough for an agent to call the tool correctly. It explains the allowance fields conceptually and covers the important behavioral details: reset time, free usage, and limits.

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?

There are zero input parameters, so parameter semantics are not a meaningful burden. The baseline for a parameterless tool is 4, and the description correctly does not invent parameter details.

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 states a specific verb and resource: it shows the caller's own allowance, including plan, daily limit, used/remaining lookups, reset time, and credit balance. This is clearly distinct from the sibling lookup/enrichment tools, which query external business data rather than account quota.

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 makes the use case clear: checking one's own allowance and limits. It gives useful context that the call is free and not counted as a lookup, which helps an agent decide to call it, but it does not explicitly say when not to use it or name alternatives.

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

All Leadgen ONRC Romania 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.