Skip to main content
Glama

LeadMarina

Get lead balance

get_balance
Read-only

What the account has left. On a plan with a rate limit this is the smaller of what the account holds and what is left in the current 7-day period (period_* describe that week, and period_resets_at is when the week resets); on a metered plan it is the account's lead balance. On a rate-limited plan with a monthly allowance, the note names the allowance when it can be read.

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Output Schema

NameRequiredDescriptionDefault
noteNo
planYes
period_usedNo
period_limitNo
leads_remainingYes
period_resets_atNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed3 schema fields changed
    • addedOutput schema / properties / period_limit
      Added value: +{
      +  "type": "number"
      +}
    • addedOutput schema / properties / period_resets_at
      Added value: +{
      +  "type": [
      +    "string",
      +    "null"
      +  ]
      +}
    • addedOutput schema / properties / period_used
      Added value: +{
      +  "type": "number"
      +}
  2. First observed

TDQS

A3.8/5.0
Behavior4/5

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

The readOnlyHint, openWorldHint=false, and destructiveHint=false annotations already establish the safety profile. The description adds useful behavioral context beyond annotations: the balance depends on the plan type, the 7-day period fields describe the current week, period_resets_at indicates the reset time, and a note may identify a monthly allowance.

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?

The description front-loads the core purpose and avoids repeating annotation or schema content. It is compact, but the nested clauses about rate-limited and metered plans make it denser and less immediately scannable than it could be.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

An output schema exists, so the description need not document the full return shape. It supplies the important plan-dependent interpretation of the balance, including what the period fields mean and when the allowance note appears, which is substantial context for a no-argument read tool.

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 here. The baseline for a zero-parameter tool applies, and the description does not need to compensate for schema gaps.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states that this returns what the account has left as a lead balance, and it distinguishes rate-limited plans from metered plans. The purpose is clear enough to distinguish it from sibling search, automation, and export tools, though the phrasing 'what the account has left' is vaguer than the title's 'Get lead balance'.

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 by the nature of the tool, but there is no explicit when-to-use or when-not-to-use guidance and no alternative balance-related tool is named. The description is more focused on interpreting the result than on advising when to call the tool.

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

Try in Browser

Glama MCP Gateway

Add one secure layer between your agents and this server.