Skip to main content
Glama

vwork_project_overview

Retrieve a snapshot of a VNFITE Work project, including account details, progress summary, open tickets, and unread notifications to assess current status.

Instructions

Ảnh chụp nhanh: tài khoản hiện tại + tổng hợp tiến độ + ticket đang mở + thông báo chưa đọc.

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

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

B3.4/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. 'Snapshot' strongly implies a read-only aggregate and the enumeration reveals which data domains are touched (account, progress, tickets, notifications), which helps an agent gauge scope and cost. It does not state that it is read-only, whether it fans out into multiple API calls, how expensive it is, or what permissions it needs.

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 compact sentence with zero filler, front-loading the 'quick snapshot' framing and then listing the four payload sections. It is efficient, though the plus-sign concatenation reads as a terse list rather than structured 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?

With no output schema and no annotations, the description does list the four content areas a caller receives, which is the essential return-value information. It omits how much data each section contains (all open tickets? truncated notifications?), the ordering or shape of the response, and whether the sections are independent or interdependent — gaps that matter for an aggregate tool.

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?

There is only one optional parameter and schema coverage is 100% — the schema already documents 'project' as a project id defaulting to VWORK_PROJECT with 'eoffice' used on the progress page. The description adds no further meaning about how the project selection scopes the returned snapshot. Baseline 3 applies when the schema does the work.

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 a concrete deliverable — a quick snapshot combining current account, progress summary, open tickets, and unread notifications — which is a specific verb-like action ('snapshot') plus an enumerated set of resources. It is clearly distinguishable from single-domain siblings like vwork_me or vwork_notifications because it aggregates across them, though it never names an alternative explicitly.

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 phrase 'Ảnh chụp nhanh' (quick snapshot) implies a use case: getting a one-shot overview rather than drilling into a specific resource. However, there is no explicit when-to-use, when-not-to-use, or pointer to the granular siblings (vwork_me, vwork_tickets, vwork_notifications) that an agent should prefer for focused queries.

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