Skip to main content
Glama

Check Dagon credit balance

dagon_balance
Read-only

Check a Dagon account key's USD credit balance, including total credits, total usage, and available credits, to monitor spending and remaining funds.

Instructions

Show the credit balance of a Dagon account key in USD: total credits, total usage, available (GET /v1/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": "dagon_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault
api_keyNoDagon account key (gk_...). Defaults to the DAGON_API_KEY environment variable.

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral context by naming the exact fields returned and the REST endpoint behind the call, which matters because there is no output schema. It stops short of disclosing whether the call itself consumes credits, is rate limited, or how auth failures surface.

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 front-loaded sentence carries the purpose, the returned values, and the endpoint with no filler. Nothing is repeated from the title and no sentence is expendable.

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 one-optional-parameter read-only tool with no output schema, the description covers purpose, return contents, and endpoint, which is enough for correct invocation. The only gap is the lack of any usage context or cost/rate side effects, which a slightly longer description could have closed.

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 the schema already documents the api_key format (gk_...) and its fallback to the DAGON_API_KEY environment variable. The description only restates that the balance belongs to a 'Dagon account key' without adding format, precedence, or error-handling detail beyond the schema, so the baseline of 3 is appropriate.

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?

The description uses a specific verb ('Show') with a precise resource ('credit balance of a Dagon account key') and enumerates the three values returned (total credits, total usage, available). It also cites the underlying endpoint (GET /v1/credits), making it clearly distinguishable from siblings such as dagon_buy_credits without opening any schema.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. An agent can infer this is a status check rather than a purchase, but the description never states the condition that should select it (e.g., verifying balance before dagon_buy_credits or dagon_confirm_purchase).

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