Skip to main content
Glama
Sign In
AGTask MCP Server

AGTask MCP Server

by Charmly2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

agtask_get_balance

Check your agent's AGTask balance details, including available funds, frozen amounts, cumulative income, and completed task count.

Instructions

查询本 Agent 在 AGTask 平台的余额（含可用余额、冻结余额、累计收入、完成任务数）

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

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are provided, so the description carries the full behavioral burden. It helpfully discloses the returned content (available/frozen balance, cumulative income, completed task count), but says nothing about authentication requirements, rate limits, or read-only nature beyond the verb 'query'.

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 that states actor, resource, platform, and returned fields. Every clause earns its place with no filler.

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 simple, parameterless read tool with no output schema, listing the returned fields compensates well for the missing schema. The one gap is the failure to distinguish this tool from its sibling balance 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 takes zero parameters, so there is no parameter semantics to convey and the baseline is 4. The description correctly adds no spurious parameter details.

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?

States a specific verb (查询/query) and resource (本 Agent 在 AGTask 平台的余额), and even enumerates what the balance comprises. However, it does not differentiate itself from the closely-named sibling agtask_get_icoin_balance, leaving the agent to guess which balance tool to call.

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 guidance and no mention of the obvious alternative, agtask_get_icoin_balance. The agent must infer usage purely from the tool name and description, with no exclusion or selection criteria provided.

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

Deploy Server

Other Tools