Skip to main content
Glama

vwork_tracker_summary

Summarize project progress by collection, status, and assignee, then count overdue tasks and tasks due within three days.

Instructions

Tổng hợp bảng tiến độ: số lượng theo collection, trạng thái, người phụ trách; đếm task quá hạn và sắp đến hạn (3 ngày).

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

Input Schema

NameRequiredDescriptionDefault
projectNoProject id, mặc định lấy từ VWORK_PROJECT (trang tiến độ dùng "eoffice")

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.5/5.0
Behavior3/5

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

No annotations are supplied, so the description carries the full burden. It does disclose the substantive behavior — that the result is an aggregation and exactly which buckets are counted, including the 3-day upcoming-due threshold — which is real value. However it never states that the operation is read-only, what happens if the project does not exist, or how the aggregation handles paging/limits across large boards.

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?

One compact sentence, front-loaded with the core purpose and then the specific metrics, with zero filler. It is slightly dense/run-on due to the semicolon-joined clauses, but nothing is redundant.

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-required-parameter read tool with no output schema, the description usefully sketches what the summary returns (per-collection, per-status, per-assignee counts plus overdue and 3-day horizon counts). Missing are the read-only guarantee and any note on result shape/ordering, but the essentials for calling it correctly are present.

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 description coverage is 100% and the single 'project' parameter is already documented in the schema, including its VWORK_PROJECT default and the 'eoffice' example. The description adds no further meaning about that parameter, so the baseline of 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?

The description states a specific verb ('Tổng hợp' — aggregate/summarize) and a specific resource (the progress board), plus the concrete facets being aggregated: counts by collection, status and assignee, and overdue / due-within-3-days task counts. That is far more specific than the name alone, but it never distinguishes this from sibling tracker tools such as vwork_tracker_docs or vwork_tracker_search.

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?

Usage is only implied: an agent can infer this is the dashboard/rollup view rather than a detail or search view. There is no explicit 'use this when you want X instead of Y' statement, no mention of alternatives, and no preconditions or exclusions.

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