Skip to main content
Glama
Sign In
tg-agent

tg-agent

by Creatfire
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Tasks

tg_tasks
Read-only

Tracks download, export, and index task status, progress, speed, ETA, overall stats, and approval queues so you can monitor workflows and decide when to pause or proceed.

Instructions

Status, progress, speed and ETA of download/export/index tasks, overall stats, and batches waiting for approval.

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

Input Schema

NameRequiredDescriptionDefault
kindNo
limitNo
fieldsNoKeep only these fields in list items (e.g. ["message_id","name","size"])
formatNocompact = lists as {columns, rows} tables; saves a lot of context for long listingsjson
statusNoall
task_idsNo

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.4/5.0
Behavior3/5

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real substance beyond that by enumerating what is reported, including overall stats and approval-queue batches, but it never says the result is a point-in-time snapshot, how limiting works, or that approval batches are actionable elsewhere.

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?

A single front-loaded sentence that enumerates the payload without filler. It is a noun phrase rather than a full sentence, but no clause is wasted.

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 six-parameter read tool with no output schema, the description conveys the shape of the response well enough to justify calling it. It is incomplete on pagination/limit behavior and on the relationship between the approval list and the approval-handling tools, which matters for a task-monitoring tool in a large sibling set.

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?

With only 33% schema coverage, the description compensates partially: 'download/export/index tasks' maps onto the kind enum and 'batches waiting for approval' maps onto the approval status value. It says nothing about limit, task_ids, or default filtering, leaving half the parameters undocumented in both places.

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 names the resource (download/export/index tasks) and the exact data returned (status, progress, speed, ETA, overall stats, approval batches), so an agent knows this is a status-reporting tool rather than a control tool. It stops short of explicitly separating itself from tg_wait_tasks or tg_task_control, which overlap in topic.

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?

Use is implied by the content: check progress/ETA or see what is awaiting approval. Nothing states when to prefer this over polling-free alternatives like tg_wait_tasks or mutation paths like tg_task_control, and no exclusions are given.

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