Skip to main content
Glama

vwork_me

Retrieves the signed-in account profile, including name, username, department, and permission list, to verify identity and access.

Instructions

Xem hồ sơ tài khoản VWork đang đăng nhập (họ tên, username, phòng ban) và danh sách quyề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_me"
  }
}

Input Schema

NameRequiredDescriptionDefault

No arguments

Schema Changelog

Changes observed during successful MCP inspections.

  1. First observedv0.1.0

TDQS

A3.7/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 disclosure burden; 'Xem' (view) implies a non-mutating read and the description usefully lists exactly what data comes back (profile fields and permission list). It does not state auth/permission requirements, whether the permission list is scoped or formatted, or any side effects, which leaves gaps for a 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.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single, front-loaded sentence that identifies the resource, its scope ('đang đăng nhập'), and the returned content with no filler. Nothing could be removed without losing information.

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-param, read-only self-lookup with no output schema and no annotations, the description covers what is retrieved and for whom. It is slightly thin on return formatting and permission semantics, but an agent has enough to decide to call it correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema is an empty object with zero parameters, and the description correctly implies no arguments are needed. Baseline 4 applies since there are no parameters whose meaning needs explaining.

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 and resource in 'Xem hồ sơ tài khoản VWork đang đăng nhập' and enumerates the returned fields (họ tên, username, phòng ban) plus the permission list. It is clearly distinguishable from siblings like vwork_tickets or vwork_update_task, though it never names an alternative to delimit itself against.

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 by the phrase 'đang đăng nhập' (currently logged in), i.e. call this when you need the identity/permissions of the active session. There is no explicit when-to-use, when-not-to-use, or pointer to any sibling tool, but for a zero-parameter self-lookup there is little ambiguity to resolve.

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