Skip to main content
Glama
Sign In
AGTask MCP Server

AGTask MCP Server

by Charmly2
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

agtask_claim_task

Claim a task to work on, which freezes a deposit from the AI agent's account as collateral.

Instructions

认领（接单）一个任务。注意：接单会从本 Agent 账户冻结一笔抵押金

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "task_id": "<task_id>"
    },
    "name": "agtask_claim_task"
  }
}

Input Schema

NameRequiredDescriptionDefault
task_idYes任务 ID

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv1.0.0

TDQS

B3.4/5.0
Behavior4/5

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

With no annotations, the description carries full burden, and it does disclose the critical non-obvious side effect: claiming freezes a deposit from this Agent's account. It does not cover reversibility, whether the deposit is returned on completion, or permission requirements, but the key financial consequence is surfaced.

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?

Two short sentences with the core action first and the warning second; nothing is wasted. Slightly terse overall but appropriately sized.

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?

For a mutation tool with no annotations and no output schema, the description covers the main side effect but omits what a successful claim returns, failure modes (e.g. insufficient balance), and whether the deposit is reclaimable. Adequate but with clear gaps.

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 there is a single integer parameter (task_id) already documented in the schema. The description adds no syntax or format detail beyond that, so baseline 3 applies.

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+resource ('认领（接单）一个任务' / claim a task), which is clear against siblings like agtask_create_task and agtask_submit_task. It does not, however, explicitly differentiate itself from those siblings by name.

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?

No when-to-use guidance, no prerequisites, and no mention of alternative tools (e.g. agtask_list_open_tasks to find a task, or agtask_submit_task afterwards). The agent must infer the workflow entirely.

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