Skip to main content
Glama

vwork_tracker_search

Search tasks and documents on a project progress board by keyword, status, assignee, collection, or overdue flag to find the work items you need.

Instructions

Tìm task/doc trong bảng tiến độ theo từ khoá, trạng thái, người phụ trách, collection hoặc chỉ task quá hạn.

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

Input Schema

NameRequiredDescriptionDefault
limitNo
queryNotừ khoá tìm trong mọi trường
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")
assigneeNolọc theo người phụ trách, khớp một phần
collectionNolọc theo collection/loại doc
overdueOnlyNochỉ lấy task quá hạn

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

B3.2/5.0
Behavior2/5

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

No annotations are supplied, so the description bears the full disclosure burden, yet it is a single sentence that omits whether the operation is read-only, how results are ordered, whether a default limit is applied, or how the implicit project resolution behaves. It conveys only the filter axes, which the schema already exposes.

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 puts the verb and resource first and packs the filter list compactly with no filler. It is efficient, though extremely terse for a seven-parameter tool.

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?

With seven optional parameters, no annotations and no output schema, the description covers the filtering intent adequately but leaves result shape, ordering, default limit (30) and project fallback (VWORK_PROJECT) to the schema alone. It is minimally sufficient rather than 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 86%, so the schema already explains query, status, assignee, collection, project and overdueOnly, giving a baseline of 3. The description merely restates those facets and adds no syntax or matching semantics (e.g. partial-match behaviour) beyond what the schema says.

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 gives a specific verb+resource: search tasks/docs in the progress board ('Tìm task/doc trong bảng tiến độ'), and enumerates the filtering facets. It does not explicitly name how it differs from siblings such as vwork_tracker_docs or vwork_my_tasks, so it falls just short of full differentiation.

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?

The facet list ('theo từ khoá, trạng thái, người phụ trách, collection hoặc chỉ task quá hạn') implies when the tool is appropriate, but there is no explicit statement of when to prefer it over sibling search/list tools, nor any prerequisites or exclusions.

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