Skip to main content
Glama

Linkup credit balance

linkup-credits-balance
Read-onlyIdempotent

Retrieve the prepaid USD credit balance to monitor available Linkup credits, avoid 429 errors when funds run out, and confirm at least 10 USD for extraction tasks.

Instructions

Return the prepaid balance in USD (GET /v1/credits/balance). Free. Linkup credits eligible accounts back up to 20 USD a month; when the balance is used up the API answers 429. Extract tasks need a balance of at least 10 USD.

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": "linkup-credits-balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A4.3/5.0
Behavior4/5

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

Annotations already declare readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely useful behavior beyond that: it is free to call, the API returns 429 when funds run out, and extract has a 10 USD minimum. It does not describe the response payload, though no output schema exists to lean on.

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?

Four short sentences, purpose front-loaded, and each one adds a distinct fact (cost, endpoint, refill policy, failure mode, extract threshold). The telegraphic fragments ('Free.') read slightly clipped but waste nothing.

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?

For a zero-parameter read tool with no output schema, the description covers purpose, cost, failure mode, and the main downstream dependency. Only the shape of the returned balance data is left unspecified, a minor gap at this complexity.

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 the baseline is 4; the description correctly implies the call takes no arguments by framing it as a plain GET on a fixed endpoint.

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 ('Return the prepaid balance in USD') and even names the underlying endpoint GET /v1/credits/balance. No sibling does anything similar, so an agent can identify 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 real decision context: the call is free, credits accounts are topped up to 20 USD monthly, exhausted balance triggers 429, and extract tasks require at least 10 USD. It does not explicitly say 'call this before running extract', but the preconditions imply it strongly; there is no alternative credit tool to route against.

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