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) 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).

Input Schema

TableJSON Schema

Name	Required	Description	Default
No arguments

Output Schema

TableJSON 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.6/5.0

Behavior5/5

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

Beyond the annotations (readOnly, idempotent, non-destructive, closed-world), the description discloses the rate-limit policy, the exact reset moment (00:00 UTC), that the call is uncounted against quota, and how to raise the limit via a free API key with no payment. This is substantive operational and auth context the annotations do not carry.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Purpose is front-loaded in the first clause, followed by the returned fields and then the cost/limit notes, so the agent gets the essential fact first. It is slightly dense with the enumerated fields plus the signup URL, but every sentence carries actionable information.

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 present, return-value exposition is not required, yet the description still names the key fields, and the safety profile is fully covered by annotations. For a zero-param 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 the baseline is 4 and there is nothing for the description to disambiguate. The enumerated return fields are a bonus rather than a substitute for missing parameter documentation.

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 and resource ('Show your own allowance') and enumerates exactly what the response contains: plan, daily limit, lookups used today, remaining count, reset time and credit balance. There is no sibling tool that overlaps with a usage/quota self-check, so differentiation is inherent and an agent can pick it instantly.

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?

It tells the agent the call is free and 'never counted as a lookup', which is a concrete usage signal, and supplies the quota ceilings (30 anonymous, 50 with a key) so the agent knows when the plan is exhausted. It does not state an explicit when-to-call trigger or name an alternative, but with a zero-parameter read tool and no competing sibling there is little else to route.

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.