Skip to main content
Glama

Show my daily allowance

get_usage
Read-onlyIdempotent

Show your own allowance: plan, daily limit, lookups used today, how many remain, when it resets (midnight Romanian time, 00:00 Europe/Bucharest) and any credit balance. Free and never counted as a lookup.

Instructions

Show your own allowance: plan, daily limit, lookups used today, how many remain, when it resets (midnight Romanian time, 00:00 Europe/Bucharest) 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

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
planNoPlan name (free, pro, business).
errorNoSet only when there is no answer (empty_query, invalid_cui, data_unavailable, plan_required ...); such a call is not counted.
linksNoget_a_key, pricing, docs.
countedNoAlways false: this call is not counted.
messageNoA sentence for the caller.
identityNoWho is counted: kind (key or anonymous) and counted_as.
remainingNoLookups left today.
resets_atNoWhen the allowance resets (ISO 8601, midnight Romanian time).
suspendedNotrue when the key is suspended.
used_todayNoLookups used today.
daily_limitNoLookups allowed per day.
entitlementsNoWhat the plan includes.
resets_in_secondsNoSeconds until the reset.

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.1.4
    • changedOutput schema / properties / daily_limit / description
      Previous value: -"Lookups allowed per UTC day."New value: +"Lookups allowed per day."
    • changedOutput schema / properties / resets_at / description
      Previous value: -"When the allowance resets (ISO 8601, 00:00 UTC)."New value: +"When the allowance resets (ISO 8601, midnight Romanian time)."
  2. First observedv0.1.0

TDQS

A4.7/5.0
Behavior5/5

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

Annotations only cover the safety profile (readOnly, idempotent, non-destructive, closed-world); the description adds far more: the operation has zero quota cost, the concrete rate limits, the exact reset boundary with timezone (00:00 Europe/Bucharest), and the upgrade path via an email-only free API key. For a quota-inspection tool these are the exact behavioral facts an agent needs before deciding whether to spend calls elsewhere.

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 sentence, front-loaded with the identifying clause 'Show your own allowance:' followed by a compact enumeration of returned fields, then the standalone facts (free, limits, reset timezone, signup URL). No filler, no repetition of the name or annotations.

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 values need not be spelled out, yet the description still names the headline fields and adds the quota economics and reset semantics that the schema cannot express. For a zero-argument read tool this leaves no meaningful gap for an agent.

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 no parameters, so there is nothing for the description to disambiguate and the baseline of 4 applies. The description correctly spends no words on arguments and instead explains the response contents.

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 is returned: plan, daily limit, lookups used today, remaining count, reset time and credit balance. No sibling tool does anything quota-related, so an agent can distinguish it immediately from the lookup/enrich tools.

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 establishes the context in which this is the right call by disclosing the quota model (30 anonymous calls/day, 50 with a free API key) and the fact that this call itself is free and not counted. It does not explicitly say 'call this when you hit a rate-limit error or before a large batch', but since no alternative tool exists for this purpose, the implicit routing is unambiguous.

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