Skip to main content
Glama
UserAd

didlogic_mcp

get_balance

Retrieve the current account balance in USD from DIDLogic via the didlogic_mcp server. Returns a JSON object with the balance for easy integration and usage.

Instructions

Get the current DIDLogic account balance

Returns a JSON object with balance in USD Example output: {"balance": 35.22}

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault

No arguments

Implementation Reference

  • The get_balance tool handler: an async function decorated with @mcp.tool() that fetches the account balance from the Didlogic API /v1/balance endpoint and returns it as a JSON string.
    @mcp.tool()
    async def get_balance(ctx: Context) -> str:
        """
            Get the current DIDLogic account balance
    
            Returns a JSON object with balance in USD
            Example output: `{"balance": 35.22}`
        """
        response = await base.call_didlogic_api(ctx, "GET", "/v1/balance")
        return response.text
  • Registers the balance tools module (including get_balance) on the FastMCP server instance.
    tools.balance.register_tools(mcp)
Behavior2/5

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the return format ('JSON object with balance in USD') and an example, which adds some context. However, it fails to disclose critical behavioral traits like whether this is a read-only operation, if it requires authentication, rate limits, or error handling. For a tool with zero annotation coverage, this is insufficient.

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?

The description is highly concise and well-structured: it states the purpose in the first sentence, provides return details in the second, and includes an example output. Every sentence adds value without waste, making it easy to scan and understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's low complexity (0 parameters, no output schema, no annotations), the description is minimally adequate. It covers the basic purpose and output format, but lacks details on authentication, error cases, or integration context. Without annotations or output schema, it should do more to compensate, but it meets the bare minimum for such a simple tool.

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 has 0 parameters, and schema description coverage is 100%, so there are no parameters to document. The description doesn't need to add parameter semantics beyond what the schema provides. A baseline of 4 is appropriate as it avoids redundancy and focuses on other aspects, though it doesn't fully earn a 5 since it doesn't explicitly state the lack of parameters.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get the current DIDLogic account balance.' It specifies the verb ('Get') and resource ('DIDLogic account balance'), making the intent unambiguous. However, it does not explicitly differentiate from sibling tools like 'get_transactions' or 'get_call_history', which might also retrieve financial or account-related data, so it doesn't fully earn a 5.

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?

The description provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites, context, or exclusions, such as whether authentication is required or if it's for real-time balance checks. With sibling tools like 'get_transactions' that might provide related financial data, the lack of comparative guidance is a significant gap.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/UserAd/didlogic_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server