Skip to main content
Glama

vwork_my_tasks

Retrieve tasks and documents assigned to the signed-in user by resolving identity from user info and matching name, username, email, or ID; filter by status, project, done, or overdue.

Instructions

Task/doc được giao cho CHÍNH tài khoản đang đăng nhập. Tự lấy danh tính từ /user/getUserInfo rồi khớp theo tên/username/email/id. Dùng khi người dùng hỏi 'tôi đang có task gì'.

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_my_tasks"
  }
}

Input Schema

NameRequiredDescriptionDefault
limitNo
statusNolọc theo trạng thái, khớp một phần
projectNoProject id, mặc định lấy từ VWORK_PROJECT (trang tiến độ dùng "eoffice")
includeDoneNogồm cả task đã xong
overdueOnlyNochỉ task quá hạn

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.6/5.0
Behavior3/5

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

With no annotations, the description carries the full burden, and it does disclose a real behavioral trait: identity is resolved automatically via /user/getUserInfo and matched by name/username/email/id. However, it says nothing about what is returned, ordering, or pagination behavior for the limit parameter, leaving meaningful gaps for a read tool with no annotation coverage.

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?

Three short sentences, front-loaded with the scope, then the identity mechanism, then the trigger. No filler, though the identity-resolution sentence is closer to implementation detail than agent-facing guidance.

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 5-parameter tool with no output schema and no annotations, the description covers purpose and identity resolution but omits return shape and how the filters interact. Adequate to call correctly, not complete.

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 80%, so the schema already documents status, project, includeDone, and overdueOnly. The description adds no parameter-level meaning beyond that, so the 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: tasks/docs assigned to the currently logged-in account, with the scoping constraint ('CHÍNH tài khoản') front and center. That scope implicitly separates it from search-style siblings like vwork_tracker_search, though no sibling is named explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

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

Gives a concrete trigger phrase ('Dùng khi người dùng hỏi "tôi đang có task gì"'), which is clear usage context. It does not state when NOT to use it or name an alternative for broader searches, so it stops short of a 5.

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