Skip to main content
Glama
Sign In

Dagon Inference

by io.github.inkwell-finance
OverviewDiscussionsAdmin

Check Dagon credit balance

dagon_balance
Read-only

Show the credit balance of your Dagon key in USD: total credits, total usage, available (GET /v1/credits). Uses the connection's Authorization: Bearer key.

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

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A4.3/5.0
Behavior4/5

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

With readOnlyHint and openWorldHint already declared, the description adds real context: values are denominated in USD, the specific fields returned, and that authentication comes from the connection's Authorization: Bearer key. It does not state whether this call itself consumes credits or mention rate limits, but the auth and return-shape details go meaningfully beyond the annotations.

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 sentence that front-loads the verb and resource, then layers in the returned fields, endpoint, and auth mechanism with no filler. Every clause carries information an agent needs.

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?

For a zero-parameter, read-only lookup with no output schema, the description supplies the return fields, currency, endpoint, and auth source — everything required to call it correctly and interpret the result. Nothing material is missing.

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?

The tool takes zero parameters, so there is no parameter meaning to add and the baseline of 4 applies. The description correctly implies no input is needed beyond the configured key, matching the empty schema.

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 states a specific verb and resource ("Show the credit balance of your Dagon key in USD") and then enumerates exactly what is returned: total credits, total usage, and available. It also names the backing endpoint (GET /v1/credits), which unambiguously separates this read-only balance check from siblings like dagon_buy_credits or dagon_confirm_purchase.

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 only implied: an agent can infer this is the tool for inspecting remaining credits, but the description never says when to prefer it (e.g., before calling dagon_buy_credits or when dagon_chat fails on quota) nor states any exclusions. A single routing clause would have moved this to a 4 or 5.

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

All Dagon Inference toolsInspect
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources