Skip to main content
Glama
Sign In
Local SEO Data

Local SEO Data

Official
by localseodata
OverviewSchemaSourceRelated ServersDiscussions(1)Admin
TypeScript
Remote

get_balance

Read-only

Verify available credits, daily spending cap, plan, and environment before running multi-step or costly SEO analyses to ensure the account has enough balance.

Instructions

Returns available credits (split into the monthly plan allowance, spent first, and the never-expiring wallet), daily spending cap, plan, and environment. Useful before running multi-step or expensive analyses to confirm the account has enough credits. Free (0 credits).

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
planYes
balanceYes
wallet_balanceNo
monthly_balanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv1.1.0
    • removedInput schema / $schema
      Removed value: -"http://json-schema.org/draft-07/schema#"
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
+  "$schema": "http://json-schema.org/draft-07/schema#",
+  "additionalProperties": true,
+  "properties": {
+    "balance": {
+      "type": "number"
+    },
+    "monthly_balance": {
+      "type": "number"
+    },
+    "plan": {
+      "additionalProperties": true,
+      "properties": {
+        "credits_per_month": {
+          "type": "number"
+        },
+        "current_period_end": {
+          "type": [
+            "string",
+            "null"
+          ]
+        },
+        "id": {
+          "type": "string"
+        },
+        "name": {
+          "type": "string"
+        }
+      },
+      "required": [
+        "id",
+        "name",
+        "credits_per_month",
+        "current_period_end"
+      ],
+      "type": "object"
+    },
+    "wallet_balance": {
+      "type": "number"
+    }
+  },
+  "required": [
+    "balance",
+    "plan"
+  ],
+  "type": "object"
+}
  2. First observedv0.1.0

TDQS

A4.5/5.0
Behavior4/5

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so safety is covered. The description adds value beyond them by disclosing the cost model ('Free (0 credits)') and the exact content of the response breakdown, including the spending order of the two credit pools — information an agent needs to interpret the result.

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?

Three short sentences, front-loaded with what is returned, then when to call it, then cost. Each sentence carries distinct information — payload contents, usage trigger, and free-call status — with no restatement of the name or title.

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?

A zero-parameter, read-only, free tool with an output schema that documents the return shape and annotations that cover the safety profile. The description adds the two things structured fields cannot: the semantic meaning of the two credit pools and the recommended call timing.

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?

Zero parameters, so there is nothing to document beyond what the empty schema already conveys; baseline applies. The description correctly avoids inventing or implying any inputs.

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?

Names a specific verb and resource ('Returns available credits') and enumerates the exact breakdown: monthly plan allowance (spent first), never-expiring wallet, daily spending cap, plan, and environment. No sibling tool in the list does anything similar, so an agent can distinguish it immediately.

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?

Gives a concrete trigger — call it before multi-step or expensive analyses to confirm sufficient credits. It does not state when the call is unnecessary (e.g., cheap single-shot queries), but with no competing sibling for balance information there is little ambiguity left.

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

Deploy Server

Other Tools