Skip to main content
Glama

AutoTasker Hub — China Social Data API

treasury_balance

Current USDC + ETH balance of the AutoTasker Hub treasury on Base. $0.01 USDC.

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": "treasury_balance"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observed

TDQS

A3.7/5.0
Behavior3/5

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

With no annotations, the description carries the disclosure burden, and it does state which assets are reported (USDC and ETH) and the chain (Base). However, it says nothing about freshness/caching, whether the read is live or snapshotted, or the shape of what comes back (two amounts? a combined USD figure?), which matters when there is no output schema.

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-loaded identity sentence with no wasted preamble. The trailing '$0.01 USDC.' is ambiguous — it reads either as a sample value or a stale cached quote — and adds uncertainty rather than clarity.

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 with no output schema, the description is nearly sufficient: it names the chain, the assets, and the owner entity. The missing piece is the return format and the meaning of the appended '$0.01 USDC' fragment, which could confuse an agent reasoning about the result.

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 input parameters, so the baseline is 4. The description correctly implies no user input is required to scope the call to a single fixed treasury.

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?

Names a specific resource and scope: the current USDC + ETH balance of the AutoTasker Hub treasury on Base. An agent can immediately distinguish this from price tools (btc_usd_rate, erapi_fx) or generic chain tools (chain_stats) 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 Guidelines2/5

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

There is no when-to-use or when-not-to-use guidance and no mention of any alternative tool. The purpose is inferable, but nothing tells the agent whether this is the right call versus chain_stats or defillama_pools for balance-related questions.

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.