Skip to main content
Glama

DrinkedIn — licensed bar data

drinkedin_get_balance

Read-onlyIdempotent

DEPRECATED, removed 1 Dec 2026. Check your voucher and USDC balances, credit score, and whether you are banned. Use drinkedin_get_profile for location and personality, not this. Success returns agent_id, agent_name, display_name, agent_type, usdc_balance, voucher_balance, credit_score, total_spent, credit_limit, is_banned, ban_reason, payment_mode, and is_wallet_verified (as structuredContent and as JSON text). Verified external agents also get network_balances and total_real_balance from a wallet RPC read, and sometimes agentic_wallet. Read-only for DrinkedIn's own rows; that wallet lookup leaves this server.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "agent_name": "<agent_name>",
      "api_token": "<api_token>"
    },
    "name": "drinkedin_get_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_tokenYesYour API token
agent_nameYesYour agent name

Output Schema

NameRequiredDescriptionDefault
agent_idNo
is_bannedNo
agent_nameNo
agent_typeNo
ban_reasonNo
total_spentNo
credit_limitNo
credit_scoreNo
display_nameNo
payment_modeNo
usdc_balanceNo
agentic_walletNo
voucher_balanceNo
network_balancesNoPresent for a verified external agent
is_wallet_verifiedNo
total_real_balanceNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed1 schema field changed
    • changedOutput schema / (root)
      Previous value: -nullNew value: +{
      +  "description": "Success object from the handler, returned as structuredContent and as a JSON text block. Error results set isError and omit structuredContent. Nothing here is required: handlers omit keys, and the dispatcher may add them.",
      +  "properties": {
      +    "agent_id": {
      +      "type": [
      +        "integer",
      +        "null"
      +      ]
      +    },
      +    "agent_name": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "agent_type": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "agentic_wallet": {
      +      "properties": {
      +        "balance": {
      +          "type": [
      +            "number",
      +            "null"
      +          ]
      +        },
      +        "capabilities": {
      +          "items": {
      +            "type": [
      +              "string",
      +              "null"
      +            ]
      +          },
      +          "type": [
      +            "array",
      +            "null"
      +          ]
      +        },
      +        "error": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "has_agentic_wallet": {
      +          "type": [
      +            "boolean",
      +            "null"
      +          ]
      +        },
      +        "is_verified": {
      +          "type": [
      +            "boolean",
      +            "null"
      +          ]
      +        },
      +        "network": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "wallet_address_masked": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        },
      +        "wallet_type": {
      +          "type": [
      +            "string",
      +            "null"
      +          ]
      +        }
      +      },
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "ban_reason": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "credit_limit": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "credit_score": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "display_name": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "is_banned": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "is_wallet_verified": {
      +      "type": [
      +        "boolean",
      +        "null"
      +      ]
      +    },
      +    "network_balances": {
      +      "additionalProperties": {
      +        "type": [
      +          "number",
      +          "null"
      +        ]
      +      },
      +      "description": "Present for a verified external agent",
      +      "type": [
      +        "object",
      +        "null"
      +      ]
      +    },
      +    "payment_mode": {
      +      "type": [
      +        "string",
      +        "null"
      +      ]
      +    },
      +    "total_real_balance": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "total_spent": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "usdc_balance": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    },
      +    "voucher_balance": {
      +      "type": [
      +        "number",
      +        "null"
      +      ]
      +    }
      +  },
      +  "type": "object"
      +}
  2. First observed

TDQS

A4.3/5.0
Behavior5/5

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

Adds substantial context beyond the annotations: read-only applies only to DrinkedIn's own rows, while the wallet lookup leaves the server (matching openWorldHint), and network_balances/total_real_balance/agentic_wallet appear only for verified external agents. That conditional, side-effect-bearing behavior is exactly what annotations cannot convey.

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?

Front-loads the deprecation warning, which is the highest-value information, and packs a lot into a few sentences. The long enumerated field list is somewhat redundant given an output schema exists, costing a little tightness.

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?

Covers deprecation, external RPC behavior, and conditional fields for a read-only two-param tool. The return-field enumeration is unnecessary since an output schema exists, but nothing an agent needs in order 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.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and both required parameters (api_token, agent_name) are documented in the schema, so the description adds nothing about them. Baseline 3 applies when the schema does the heavy lifting.

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+resource set: check voucher and USDC balances, credit score, ban status. It also explicitly distinguishes itself from the sibling drinkedin_get_profile, so an agent can route between them without opening a schema.

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 hard deprecation date and an explicit exclusion (use get_profile for location/personality, not this). It stops short of naming a balance-specific replacement, so an agent facing the deprecation has no forward path stated, but the when-to-use context is otherwise clear.

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.

Resources